Title

The container platform must automatically disable accounts after a 35-day period of account inactivity. (Cat II impact)

Discussion

Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need to track periods of user inactivity and disable accounts after 35 days of inactivity. Such a process greatly reduces the risk that accounts will be hijacked, leading to a data compromise. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality. This policy does not apply to either emergency accounts or infrequently used accounts. Infrequently used accounts are local login administrator accounts used by system administrators when network or normal logon/access is not available. Emergency accounts are administrator accounts created in response to crisis situations.

Check Content

Determine if the container platform automatically disables accounts after a 35-day period of account inactivity. If the container platform does not automatically disable accounts after a 35-day period of account inactivity, this is a finding.

Fix Text

Configure the container platform to automatically disable accounts after a 35-day period of account inactivity.

Additional Identifiers

Rule ID: SV-233021r879524_rule

Vulnerability ID: V-233021

Group Title: SRG-APP-000025

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.