# Ensure System Warns When Audit Logs Are Low on Space (Automated)

- Source: https://support.icompaas.com/support/solutions/articles/62000235492-ensure-system-warns-when-audit-logs-are-low-on-space-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 define actions to take when disk space allocated for audit logs is low. Configuring these settings to send warnings helps notify administrators before the disk space is exhausted, allowing proactive management of audit logs.

### **Rationale:**

Warnings about low disk space on audit logs help ensure that audit logging continues uninterrupted and that corrective actions can be taken before the system reaches a critical state where audit logs can no longer be written.

### **Impact:**

**Pros:**  
Enables timely alerts for audit log storage issues  
Prevents unexpected audit log disruptions  
Supports compliance and forensic readiness

**Cons:**  
Requires monitoring and response process to be effective

### **Default Value:**

Defaults may vary; some systems may use `ignore` or `syslog` by default.

### **Pre-requisites:**

-   `auditd` must be installed
    
-   Root or `sudo` privileges required
    

### **Test Plan:**

**Using Linux Command Line:**

1.  Check the current `space_left_action` and `admin_space_left_action` settings:  
    
    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 auditd configuration file:
    
    vi /etc/audit/auditd.conf
    
2.  Set the following values to send warnings:
    
    space\_left\_action = email
    admin\_space\_left\_action = email
    
3.  Configure the email recipient in the `action_mail_acct` setting:
    
    action\_mail\_acct = root
    
4.  Save and exit the file.
    
5.  Restart the auditd service to apply changes:
    
    systemctl restart auditd
    

### **Backout Plan:**

**Using Linux Command Line:**

1.  Reopen the configuration file:
    
    vi /etc/audit/auditd.conf
    
2.  Restore `space_left_action` and `admin_space_left_action` to previous values (e.g., `syslog`, `ignore`).
    
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.
