STIGQter: STIG Summary: Red Hat Enterprise Linux 8 Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 23 Apr 2021:

Successful/unsuccessful modifications to the faillock log file in RHEL 8 must generate an audit record.

DISA Rule

SV-230466r627750_rule

Vulnerability Number

V-230466

Group Title

SRG-OS-000062-GPOS-00031

Rule Version

RHEL-08-030590

Severity

CAT II

CCI(s)

• CCI-000169 - The information system provides audit record generation capability for the auditable events defined in AU-2 a. at organization-defined information system components.

Weight

10

Fix Recommendation

Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "faillock" file by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:

-w /var/log/faillock -p wa -k logins

The audit daemon must be restarted for the changes to take effect.

Check Contents

Verify RHEL 8 generates an audit record when successful/unsuccessful modifications to the "faillock" file occur. First, determine where the faillock tallies are stored with the following commands:

For RHEL versions 8.0 and 8.1:

$ sudo grep -i pam_faillock.so /etc/pam.d/system-auth

auth required pam_faillock.so preauth dir=/var/log/faillock silent deny=3 fail_interval=900 even_deny_root

For RHEL versions 8.2 and newer:

$ sudo grep dir /etc/security/faillock.conf

dir=/var/log/faillock

Using the location of the faillock log file, check that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":

$ sudo grep -w faillock /etc/audit/audit.rules

-w /var/log/faillock -p wa -k logins

If the command does not return a line, or the line is commented out, this is a finding.

Vulnerability Number

V-230466

Documentable

False

Rule Version

RHEL-08-030590

Severity Override Guidance

Verify RHEL 8 generates an audit record when successful/unsuccessful modifications to the "faillock" file occur. First, determine where the faillock tallies are stored with the following commands:

For RHEL versions 8.0 and 8.1:

$ sudo grep -i pam_faillock.so /etc/pam.d/system-auth

auth required pam_faillock.so preauth dir=/var/log/faillock silent deny=3 fail_interval=900 even_deny_root

For RHEL versions 8.2 and newer:

$ sudo grep dir /etc/security/faillock.conf

dir=/var/log/faillock

Using the location of the faillock log file, check that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":

$ sudo grep -w faillock /etc/audit/audit.rules

-w /var/log/faillock -p wa -k logins

If the command does not return a line, or the line is commented out, this is a finding.

Check Content Reference

M

Target Key

2921

Comments