OL 8 systems, versions 8.2 and above, must ensure account lockouts persist.
An XCCDF Rule
Description
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. In OL 8.2, the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the "pam_faillock.so" module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in "/etc/passwd" and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout. From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be reenabled after system reboot. If that is undesirable, a different tally directory must be set with the "dir" option. Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128
- ID
- SV-248659r958388_rule
- Version
- OL08-00-020017
- Severity
- Medium
- References
- Updated
Remediation Templates
A Manual Procedure
Configure OL 8 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