# Ensure system is disabled when audit logs are full (Automated)

- Source: https://support.icompaas.com/support/solutions/articles/62000235491-ensure-system-is-disabled-when-audit-logs-are-full-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:**

The `space_left_action` and `admin_space_left_action` parameters in the `auditd` configuration determine what happens when disk space for audit logs is low or full. Configuring these settings to halt the system helps prevent it from operating without audit logging, which could result in missed events or non-compliance.

### **Rationale:**

When the system continues running without the ability to write audit logs due to full disk space, critical security events may not be recorded. Halting the system enforces the importance of auditing and protects against operating in a non-auditable state.

### **Impact:**

**Pros:**  
Ensures no activity occurs without audit logging  
Supports regulatory and forensic requirements  
Prevents loss of critical security data

**Cons:**  
May cause system downtime when disk space is full  
Requires disk space monitoring and alerting strategy

### **Default Value:**

Defaults may vary; many systems use `ROTATE` or `SUSPEND`, which allow continued operation without logging.

### **Pre-requisites:**

-   `auditd` must be installed
    
-   Root or `sudo` access is required
    

### **Test Plan:**

**Using Linux Command Line:**

1.  Check current values in the configuration file:
    
    grep "space\_left\_action" /etc/audit/auditd.conf
    grep "admin\_space\_left\_action" /etc/audit/auditd.conf
    

### **Implementation Plan:**

**Using Linux Command Line:**

1.  Open the configuration file:
    
    vi /etc/audit/auditd.conf
    
2.  Locate or add the following lines:
    
    space\_left\_action = halt
    admin\_space\_left\_action = halt
    
3.  Save and exit the file.
    
4.  Restart the auditd service:
    
    systemctl restart auditd
    

### **Backout Plan:**

**Using Linux Command Line:**

1.  Reopen the configuration file:
    
    vi /etc/audit/auditd.conf
    
2.  Change the values of `space_left_action` and `admin_space_left_action` back to their previous settings (e.g., `rotate`, `suspend`, or `exec`).
    
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-5

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