# Ensure audit_backlog_limit is sufficient (Automated)

- Source: https://support.icompaas.com/support/solutions/articles/62000235486-ensure-audit-backlog-limit-is-sufficient-automated-
- 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:**

In some cases, processes may start before the `auditd` service is initialized. Ensuring auditing for these processes is enabled allows system administrators to capture important events even if the process starts before the audit subsystem is fully active.

### **Rationale:**

Enabling auditing for early-start processes ensures that all critical system activities, including those occurring before the audit service starts, are logged. This improves overall system monitoring, accountability, and security posture by capturing actions that could otherwise evade audit logging.

### **Impact:**

**Pros:**  
Captures system events that would otherwise be missed.  
Helps with forensic investigations and security incident detection from process startups.

**Cons:**  
May slightly increase system overhead by capturing more data.

### **Default Value:**

By default, auditing for processes that start before `auditd` is activated may not be enabled unless explicitly configured.

### **Pre-requisites:**

Root or `sudo` privileges to modify audit settings.

### **Test Plan:**

**Using Linux Command Line:**

1.  Check if auditing is set up to capture early-start processes:
    

`grep "audit" /etc/audit/auditd.conf   `

2.  Verify the audit control status:
    

`sysctl kernel.audit_ctrl   `

3.  Ensure the `audit_backlog_limit` is set to an appropriate value in the configuration.
    

### **Implementation Plan:**

**Using Linux Command Line:**

1.  Open the `auditd` configuration file:
    

`vi /etc/audit/auditd.conf   `

2.  Ensure the following option is set with a sufficient backlog limit:
    

`audit_backlog_limit = 8192   `

            (Adjust the value based on your system’s needs.)

3.  Reload or restart `auditd` to apply the changes:
    

`systemctl restart auditd   `

### **Backout Plan:**

**Using Linux Command Line:**

1.  Reopen the configuration file:
    

`vi /etc/audit/auditd.conf   `

2.  Restore the previous `audit_backlog_limit` value or remove the line if it was added during implementation.
    
3.  Restart the `auditd` service:
    

`systemctl restart auditd   `

### **References:**

CIS Amazon Linux 2 Benchmark v3.0.0  
Auditd Configuration Documentation  
NIST SP 800-53 Revision 5 - 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.
