SLEM 5 must generate audit records for all uses of the "delete_module" system call.

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.

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

Verify SLEM 5 generates an audit record for all uses of the "delete_module" system call with the following command:

     > sudo auditctl -l | grep -w 'delete_module'
     -a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=-1 -F key=unload_module
     -a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -F key=unload_module

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

Note: The "key=" value is arbitrary and can be different from the example output above.

Configure SLEM 5 to generate an audit record for all uses of the "delete_module" system call.

Add or modify the following lines in the "/etc/audit/rules.d/audit.rules" file:

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

To reload the rules file, restart the audit daemon:

     > sudo systemctl restart auditd.service

or issue the following command:

     > sudo augenrules --load