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

STIG ID: SLES-12-010070  |  SRG: SRG-OS-000028-GPOS-00009 |  Severity: low |  CCI: CCI-000060,CCI-000056,CCI-000058,CCI-000057 |  Vulnerability Id: V-217108 | 

Vulnerability 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

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

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

# sudo zypper install kbd