RHEL 9 must ensure account lockouts persist.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-258060 | SRG-OS-000021-GPOS-00005 | RHEL-09-411105 | SV-258060r1045150_rule | 2025-02-27 | 2 |
| 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. |
| ℹ️ Check |
|---|
| 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 |
|---|
| 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 |