Vulnerability Discussion

Without generating audit records that are 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.

Audit records can be generated from various components within the information system (e.g., module or policy filter).

Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222

Check

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

Check the auditing rules in "/etc/audit/audit.rules" with the following command:

$ sudo grep -w "delete_module" /etc/audit/audit.rules

-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module-change

-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module-change

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

Fix

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

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

-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module-change

-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module-change

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