The IBM z/VM Security Manager must provide a procedure to disable userIDs after 35 days of inactivity.

From IBM z/VM Using CA VM:Secure Security Technical Implementation Guide

Associated with: CCI-000795

SV-93591r1_rule The IBM z/VM Security Manager must provide a procedure to disable userIDs after 35 days of inactivity.

Vulnerability 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.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.