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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-237919	SRG-OS-000118-GPOS-00060	IBMZ-VM-000650	SV-237919r649597_rule	2022-08-31	2

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

ℹ️ Check

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