OL 9 must ensure account lockouts persist.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-271842OL09-00-003023SV-271842r1092238_ruleCCI-000044medium
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.
STIGDate
Oracle Linux 9 Security Technical Implementation Guide2025-05-08

Related Frameworks

3 paths across 3 frameworks
NIST 800-531 mapping
AC-7
1.00
  • DISA · 1 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.8
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-000044
1.00
  • DISA · 1 · disa_xccdf · related

Details

Check Text (C-271842r1092238_chk)

Verify that OL 9 ensures that account lockouts persist. Verify the "/etc/security/faillock.conf" file is configured use a nondefault faillock directory to ensure contents persist after reboot with the following command: $ grep 'dir =' /etc/security/faillock.conf dir = /var/log/faillock If the "dir" option is not set to a nondefault documented tally log directory, is missing or commented out, this is a finding.

Fix Text (F-75799r1092237_fix)

Configure OL 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