RHEL 9 must ensure account lockouts persist.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-258060 | RHEL-09-411105 | SV-258060r1045150_rule | CCI-000044 | medium |
| Description | ||||
| Having lockouts persist across reboots ensures that account is only unlocked by an administrator. If the lockouts did not persist across reboots, an attacker could simply reboot the system to continue brute force attacks against the accounts on the system. | ||||
| STIG | Date | |||
| Red Hat Enterprise Linux 9 Security Technical Implementation Guide | 2025-05-14 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
AC-7
1.00
- DISA · 2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.8
1.00
- DISA · 2 · 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-000044
1.00
- DISA · 2 · disa_xccdf · related
Details
Check Text (C-258060r1045150_chk)
Verify the "/etc/security/faillock.conf" file is configured to use 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 or is missing or commented out, this is a finding.
Fix Text (F-61725r926166_fix)
Configure RHEL 9 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