# Ensure Audit Logging of Kernel Module Load, Unload, and Modification Events

- Source: https://support.icompaas.com/support/solutions/articles/62000234988-ensure-audit-logging-of-kernel-module-load-unload-and-modification-events
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS Amazon Linux 2 Benchmark v3.0.0](https://support.icompaas.com/support/solutions/62000112696) › [CIS Amazon Linux 2 Benchmarks](https://support.icompaas.com/support/solutions/folders/62000169265)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Profile Applicability: **• Level 2**

Description:  
 Kernel modules extend the functionality of the operating system. Monitoring and auditing module loading, unloading, and modifications is critical to detect unauthorized or malicious activity that could compromise system security.

Rationale:  
 Collecting audit logs for kernel module events provides visibility into critical changes, enabling timely detection of suspicious activities and maintaining system integrity.

Impact:  
 Pros:

-   Enhances detection of unauthorized kernel module manipulations.  
    
-   Supports forensic investigations and compliance requirements.  
    

Cons:

-   May increase audit log volume and require log management.  
    

Default Value:  
 Audit rules for kernel module events may not be enabled by default.

Pre-requisites:

-   Root or sudo privileges to configure audit rules.  
    

Remediation:

### Test Plan:

Using Linux command line:

Check current audit rules for kernel module events:

auditctl -l | grep 'module' 

Verify audit rules exist for syscall init\_module, delete\_module, and relevant file watches.

  

### Implementation Plan:

Using Linux command line:

Add audit rules to monitor kernel module events:

auditctl -w /sbin/insmod -p x -k module-change  
auditctl -w /sbin/rmmod -p x -k module-change  
auditctl -a always,exit -F arch=b64 -S init\_module -S delete\_module -k module-change

Persist rules by adding them to /etc/audit/rules.d/audit.rules.  

### Backout Plan:

Using Linux command line:

Remove kernel module audit rules as needed:

auditctl -W /sbin/insmod -p x -k module-change  
auditctl -W /sbin/rmmod -p x -k module-change  
auditctl -D -k module-change

Reload audit daemon configuration.  

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   [Linux Audit Framework  
    ](https://linux-audit.com/)
    
-   [NIST SP 800-53 Revision 5 - AU-6  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#au-6)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
