Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
AlmaLinux OS 9 must ensure account locks persist across reboots.
Description
Discussion Text
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.
Having account locks persist across reboots ensures that a locked account is only unlocked by an administrator.
If the locks did not persist across reboots, an attacker could reboot the system to continue brute force attacks against the accounts on the system.
The default /var/run/faillock directory is cleared upon reboot and should not be used.
Having account locks persist across reboots ensures that a locked account is only unlocked by an administrator.
If the locks did not persist across reboots, an attacker could reboot the system to continue brute force attacks against the accounts on the system.
The default /var/run/faillock directory is cleared upon reboot and should not be used.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.