STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM Aspera Platform 4.2 Security Technical Implementation Guide

V-252634

CAT II (Medium)

The IBM Aspera High-Speed Transfer Server must enable the use of dynamic token encryption keys.

Rule ID

SV-252634r818072_rule

STIG

IBM Aspera Platform 4.2 Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-000068CCI-000197

Discussion

Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. The dynamic token encryption key is used for encrypting authorization tokens dynamically for improved security and time-limited validity which limits the chances of a key becoming compromised. NOTE: A dynamic token encryption key can be set for an individual user or a system group. Satisfies: SRG-NET-000062-ALG-000011, SRG-NET-000400-ALG-000097

Check Content

Verify the Aspera High-Speed Transfer Server enables the use of dynamic token encryption keys with the following command:

$ sudo /opt/aspera/bin/asuserdata -a | grep dynamic

token_dynamic_key: "true"

If the "dynamic_key" setting is not set to "true", this is a finding.

Fix Text

Configure the Aspera High-Speed Transfer Server to enable the use of dynamic token encryption keys with the following command:

$ sudo asconfigurator -x "set_node_data; token_dynamic_key,true"

Restart the IBM Aspera Node service to activate the changes.

$ sudo systemctl restart asperanoded.service