Vulnerability Discussion

If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.

When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and "unset" in the same way.

Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00211, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172

Check

Verify the operating system generates audit records when successful/unsuccessful attempts to use the "rmdir" syscall occur.

Check the file system rules in "/etc/audit/audit.rules" with the following commands:

# grep -iw rmdir /etc/audit/audit.rules

-a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=unset -k delete

-a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=unset -k delete

If both the "b32" and "b64" audit rules are not defined for the "rmdir" syscall, this is a finding.

Fix

Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "rmdir" syscall occur.

Add the following rules in "/etc/audit/rules.d/audit.rules":

-a always,exit -F arch=b32 -S rmdir -F auid>=1000 -F auid!=unset -k delete

-a always,exit -F arch=b64 -S rmdir -F auid>=1000 -F auid!=unset -k delete

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