Check: SLES-15-010110
SUSE Linux Enterprise Server 15 STIG:
SLES-15-010110
(in versions v2 r3 through v1 r1)
Title
The SUSE operating system must utilize vlock to allow for session locking. (Cat III impact)
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 search --installed-only --match-exact --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
Additional Identifiers
Rule ID: SV-234811r1009610_rule
Vulnerability ID: V-234811
Group Title: SRG-OS-000028-GPOS-00009
Expert Comments
CCIs
Number | Definition |
---|---|
CCI-000056 |
Retain the device lock until the user reestablishes access using established identification and authentication procedures. |
CCI-000057 |
Prevent further access to the system by initiating a device lock after organization-defined time period of inactivity; and/or requiring the user to initiate a device lock before leaving the system unattended. |
CCI-000058 |
The information system provides the capability for users to directly initiate session lock mechanisms. |
CCI-000060 |
Conceal, via the device lock, information previously visible on the display with a publicly viewable image. |