Skip to content

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

An XCCDF Rule

Description

<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID
SV-252649r831535_rule
Severity
Medium
References
Updated



Remediation - Manual Procedure

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.