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 6 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to SLES 12 Security Technical Implementation Guide

V-217108

CAT III (Low)

The SUSE operating system must utilize vlock to allow for session locking.

Rule ID

SV-217108r1015204_rule

STIG

SLES 12 Security Technical Implementation Guide

Version

V3R2

CCIs

V-77059

Discussion

A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. The session lock is implemented at the point where session activity can be determined. Regardless of where the session lock is determined and implemented, once invoked, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system. Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011, SRG-OS-000031-GPOS-00012

Check Content

Check that the SUSE operating system has the "vlock" package installed by running the following command: 

# zypper se -i --provides vlock 

If the command outputs "no matching items found", this is a finding.

Fix Text

Allow users to lock the console by installing the "kbd" package using zypper:

# sudo zypper install kbd