Vulnerability Discussion

Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.

Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218

Check

Verify RHEL 10 generates audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/faillock" with the following command:

$ sudo auditctl -l | grep /var/log/faillock
-a always,exit -F arch=b32 -F path=/var/log/faillock -F perm=wa -F key=identity
-a always,exit -F arch=b64 -F path=/var/log/faillock -F perm=wa -F key=identity

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

Fix

Configure RHEL 10 to generate audit records for all account creations, modifications, disabling, and termination events that affect "/var/log/faillock".

Add or update the following file system rule to "/etc/audit/rules.d/audit.rules":

-a always,exit -F arch=b32 -F path=/var/log/faillock -F perm=wa -F key=identity
-a always,exit -F arch=b64 -F path=/var/log/faillock -F perm=wa -F key=identity

Restart the audit daemon with the following command for the changes to take effect:

$ sudo service auditd restart