4.1.3.31 Ensure audit of the create_module syscall - 32 bit

Information

The operating system must audit all uses of the create_module syscall.

Rationale:

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).

Solution

Configure the operating system to generate audit records when successful/unsuccessful attempts to use the create_module syscall occur.
Add or update the following rules in /etc/audit/rules.d/audit.rules:
Example: vim /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.
Add, uncomment or update the following line appropriate for the architecture you are running.

-a always,exit -F arch=b32 -S create_module -k module-change

-a always,exit -F arch=b64 -S create_module -k module-change

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

# service auditd restart

See Also

https://workbench.cisecurity.org/files/3636

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-12c., CCI|CCI-000172, CSCv7|6.2, Rule-ID|SV-204559r603261_rule, STIG-ID|RHEL-07-030819

Plugin: Unix

Control ID: e5b642bacc6a19ebbbb5394ecc2908b62e39d32148a5d2249972d76836ce2fc5