SLEM 5 must use vlock to allow for session locking.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-261276	SRG-OS-000028-GPOS-00009	SLEM-05-215010	SV-261276r996316_rule	2024-06-04	1

Description
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.

Description

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
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
Allow users to lock the console by installing the "kbd" package using zypper: > sudo transactional-update pkg install kbd > sudo reboot