OL 8 systems below version 8.2 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. OL 8 can use the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program. From "Pam_Faillock" 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-248658r958388_rule
Version: OL08-00-020016
Severity: Medium
References: CCI-000044 CCI-002238
Updated: about 2 months ago

Remediation Templates

Configure the operating system maintain the contents of the faillock directory after a reboot. 
 
Add/modify the appropriate sections of the "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" files to match the following lines. 
 
Note: Using the default faillock directory of "/var/run/faillock" will result in the contents being cleared in the event of a reboot. 
 auth required pam_faillock.so preauth dir=/var/log/faillock silent audit deny=3 even_deny_root fail_interval=900 unlock_time=0 
auth required pam_faillock.so authfail dir=/var/log/faillock unlock_time=0 
account required pam_faillock.so 
 
The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command: 
 
$ sudo systemctl restart sssd.service

OL 8 systems below version 8.2 must ensure account lockouts persist.

Description

Remediation Templates

A Manual Procedure