Title

CA-ACF2 userids found inactive for more than 35 days must be suspended. (Cat II impact)

Discussion

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. Operating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.

Check Content

From the ISPF Command Shell enter: ACF If every user shows an ACC-DATE=mm/dd/yy within the past 35 days, this is not a finding. NOTE: VALID FOR INTERACTIVE USERIDS, NOT VALID FOR STARTED TASK USERIDS AND BATCH USERIDS.

Fix Text

Develop a procedure to check all userids for inactivity more than 35 days. If found, the ISSO must suspend an account, but not delete it until it is verified by the local ISSO that the user no longer requires access. If verification is not received within 60 days, the account may be deleted.

Additional Identifiers

Rule ID: SV-223498r533198_rule

Vulnerability ID: V-223498

Group Title: SRG-OS-000118-GPOS-00060

Expert Comments

CCIs tied to check.

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