# Ensure Audit Configuration Files Have Permissions Set to 640 or More Restrictive

- Source: https://support.icompaas.com/support/solutions/articles/62000235449-ensure-audit-configuration-files-have-permissions-set-to-640-or-more-restrictive
- 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: Audit configuration files define the auditing rules and policies on the system. Setting file permissions to 640 or more restrictive ensures that only the owner (root) can modify the files and the group can read them, while others have no access. This helps protect the audit configuration from unauthorized modification.

Rationale: Restricting permissions on audit configuration files maintains the integrity and confidentiality of audit policies, preventing unauthorized changes that could disable or alter auditing.

**Impact:** **Pros:**

-   Protects audit configurations from unauthorized modifications.  
    
-   Ensures only privileged users have access to audit rules.  
    

**Cons:**

-   Overly restrictive permissions might impact legitimate access by audit services.  
    

Default Value:  
 Permissions may vary; verification and correction may be required.

Pre-requisites:

-   Root or sudo privileges to audit and modify file permissions  
    

Remediation:

### Test Plan:

Using Linux command line:

1.  Check current permissions of audit configuration files:
    
    ls -l /etc/audit/audit.rules /etc/audit/rules.d/
    
2.  Verify files have permissions set to 640 or more restrictive (e.g., 600).  
    

###   

### Implementation Plan:

Using Linux command line:

1.  Set permissions to 640 for audit configuration files:
    
    chmod 640 /etc/audit/audit.rules  
    chmod -R 640 /etc/audit/rules.d/
    

2.  Verify changes:
    
    ls -l /etc/audit/audit.rules /etc/audit/rules.d/
    

### Backout Plan:

Using Linux command line:

1.  Restore previous permissions from backups if necessary.  
    
2.  Confirm audit services function correctly after changes.  
    

References:

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

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