From Red Hat Enterprise Linux 7 Security Technical Implementation Guide
Part of SRG-OS-000471-GPOS-00216
Associated with: CCI-000172
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.
Verify the operating system generates audit records when successful/unsuccessful attempts to use the "init_module" syscall occur. Check the auditing rules in "/etc/audit/audit.rules" with the following command: Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present. # grep -iw init_module /etc/audit/audit.rules -a always,exit -F arch=b32 -S init_module -k module-change -a always,exit -F arch=b64 -S init_module -k module-change If there are no audit rules defined for "init_module", this is a finding.
Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "init_module" syscall occur. Add or update the following rules in "/etc/audit/rules.d/audit.rules": Note: The rules are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be configured. -a always,exit -F arch=b32 -S init_module -k module-change -a always,exit -F arch=b64 -S init_module -k module-change The audit daemon must be restarted for the changes to take effect.
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer