IBM Aspera Faspex must disable account identifiers after 35 days of inactivity.

An XCCDF Rule

Description

<VulnDiscussion>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID: SV-252579r817907_rule
Severity: Medium
References: CCI-000795
Updated: over 1 year ago

Configure IBM Aspera Faspex to disable account identifiers after 35 days of inactivity: 

- Log in to the IBM Aspera Faspex web page as a user with administrative privilege. 
- Select the "Server" tab.
- Select the "Configuration" tab.
- Select the "Security" section.- Under the "Faspex accounts" "Remove users" section, edit the following:
- Put a check in the "Local users" option check box.
- Edit the "Local users" option to "35" days or less.
- Put a check in the "DS users" option check box.
- Edit the "DS users" option to "35" days or less.
- Put a check in the "SAML users" option check box.
- Edit the "SAML users" option to "35" days or less.
- Select "Update" at the bottom of the page.

IBM Aspera Faspex must disable account identifiers after 35 days of inactivity.

Description

Remediation - Manual Procedure