STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM zVM Using CA VM:Secure Security Technical Implementation Guide

V-237919

CAT II (Medium)

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

Rule ID

SV-237919r649597_rule

STIG

IBM zVM Using CA VM:Secure Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000795

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.