Rule ID
SV-288139r1252649_rule
Version
V1R0.1
CCIs
Inactive identifiers pose a risk to systems and applications. Attackers that are able to exploit an inactive identifier can potentially obtain and maintain undetected access to the application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications must track periods of inactivity and disable application identifiers after 35 days of inactivity. Management of user identifiers is not applicable to shared information system accounts (e.g., guest and anonymous accounts). It is commonly the case that a user account is the name of an information system account associated with an individual. To avoid having to build complex user management capabilities directly into their application, developers leverage the underlying OS or other user account management infrastructure (AD, LDAP) already in place within the organization that meets organizational user account management requirements.
Navigate to the account configuration function within the application. Verify the application is configured to disable all identifiers after 35 days (or less) of inactivity. Otherwise, this is a finding. If a break glass or service account remains, this must be documented and approved by the authorizing official (AO). Otherwise, this is a finding.
Navigate to the account configuration function within the application. Configure a policy to disable all identifiers after 35 days (or less) of inactivity. If a break glass or service account remains, this must be documented and approved by the AO. Otherwise, this is a finding.