BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

RHEL-10-600430 RHEL 10 must ensure account lockouts persist.

DISA STIG library V1R3
All changes in this version
first version loaded CAT II

Maps to AC-7 via CCI-000044, CCI-002238

Title

RHEL 10 must ensure account lockouts persist.

Control

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.

Discussion

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

Related controls

CCI-000044, CCI-002238

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