RHEL 10 must ensure account lockouts persist.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-281198 | RHEL-10-600430 | SV-281198r1166546_rule | CCI-000044 | medium |
| Description | ||||
| Having lockouts persist across reboots ensures that an account is unlocked only by an administrator. If the lockouts did not persist across reboots, an attacker could reboot the system to continue brute force attacks against the accounts on the system. Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128 | ||||
| STIG | Date | |||
| Red Hat Enterprise Linux 10 Security Technical Implementation Guide | 2026-03-11 | |||
Details
Check Text (C-281198r1166546_chk)
Verify RHEL 10 is configured so that the "/etc/security/faillock.conf" file uses a nondefault "faillock" directory to ensure contents persist after reboot with the following command:
$ sudo grep -w dir /etc/security/faillock.conf
dir = /var/log/faillock
If the "dir" option is not set to a nondefault documented tally log directory, is commented out, or is missing, this is a finding.
Fix Text (F-85664r1166545_fix)
Configure RHEL 10 to maintain the contents of the "faillock" directory after a reboot.
Add/modify the "/etc/security/faillock.conf" file to match the following line:
dir = /var/log/faillock