← Back to IBM Aspera Platform 4.2 Security Technical Implementation Guide

V-252649

CAT II (Medium)

The IBM Aspera High-Speed Transfer Server must prohibit the use of cached authenticators after an organization-defined time period.

Rule ID

SV-252649r831535_rule

STIG

IBM Aspera Platform 4.2 Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-002007

Discussion

If the cached authenticator information is out of date, the validity of the authentication information may be questionable. This requirement applies to all ALGs that may cache user authenticators for use throughout a session. It also applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management).

Check Content

Verify the IBM Aspera High-Speed Transfer Server prohibits the use of cached authenticators after an organization-defined time period with the following command:

$ sudo /opt/aspera/bin/asuserdata -a | grep 'token_life'

token_life_seconds: "86400"

Note: The example token life is for one day; this number must be defined by the organization.

If no result is returned or if the result is not an organization-defined time period, this is a finding.

Fix Text

Configure the IBM Aspera High-Speed Transfer Server to prohibit the use of cached authenticators after an organization-defined time period with the following command:

$ sudo /opt/aspera/bin/asconfigurator -x "set_node_data;token_life_seconds,86400"

Restart the IBM Aspera Node service to activate the changes.

$ sudo systemctl restart asperanoded.service