SLEM 5 must use vlock to allow for session locking.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-261276 | SLEM-05-215010 | SV-261276r996316_rule | CCI-000056 | medium |
| 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. | ||||
| STIG | Date | |||
| SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide | 2025-05-08 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
AC-11
1.00
- DISA · 1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.10
1.00
- DISA · 1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000056
1.00
- DISA · 1 · disa_xccdf · related
Details
Check Text (C-261276r996316_chk)
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 (F-64913r995694_fix)
Allow users to lock the console by installing the "kbd" package using zypper:
> sudo transactional-update pkg install kbd
> sudo reboot