Title

The IBM z/VM Security Manager must provide a procedure to disable userids after 35 days of inactivity. (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

Examine the procedure for disabling user accounts. If the procedure performs the following steps, this is not a finding. - Monitors the time since last logon. - Checks 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.

Fix Text

Develop a procedure that includes the following steps: - Monitors the time since last logon. - Checks 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:

Vulnerability ID: IBMZ-VM-000650

Group Title:

Expert Comments

CCIs tied to check.

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