Check: SLEM-05-215010
SUSE Linux Enterprise Micro (SLEM) 5 STIG:
SLEM-05-215010
(in version v1 r1)
Title
SLEM 5 must use vlock to allow for session locking. (Cat II 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.
Check Content
Check that SLEM 5 has the "vlock" package installed with the following command: > zypper search --installed-only --match-exact --provides vlock i | kbd | Keyboard and Font Utilities | package 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 transactional-update pkg install kbd > sudo reboot
Additional Identifiers
Rule ID: SV-261276r996316_rule
Vulnerability ID: V-261276
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-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. |