# Ensure Audit Tools Have Permissions Set to 755 or More Restrictive

- Source: https://support.icompaas.com/support/solutions/articles/62000235445-ensure-audit-tools-have-permissions-set-to-755-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 1

Description: Audit tools are vital for monitoring and logging system activities. Setting file permissions to 755 or more restrictive ensures that only authorized users can modify or execute these tools, maintaining their integrity and preventing unauthorized access.

Rationale: Proper permissions prevent unauthorized modification or misuse of audit tools, protecting the accuracy and reliability of audit logs and system security.

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

-   Secures audit tools against unauthorized changes.  
    
-   Allows necessary execution permissions for legitimate users.  
    

**Cons:**

-   Overly restrictive permissions may interfere with legitimate audit operations if misconfigured.  
    

Default Value: Audit tools may have varying permissions; verification and correction are needed.

Pre-requisites:

-   Root or sudo privileges to audit and modify file permissions.  
    

Remediation:

### Test Plan:

Using Linux command line:

1.  List audit tool files and their permissions:
    
    ls -l /sbin/audit\* /usr/sbin/audit\*
    
2.  Verify permissions are set to 755 or more restrictive (e.g., 750, 700).  
    

### Implementation Plan:

Using Linux command line:

1.  Set permissions to 755 or more restrictive as appropriate:
    
    chmod 755 /sbin/audit\* /usr/sbin/audit\*
    
2.  Verify changes:
    
    ls -l /sbin/audit\* /usr/sbin/audit\*
    

### Backout Plan:

Using Linux command line:

1.  Restore previous permissions from backups if necessary.  
    
2.  Test audit tools to ensure proper functionality.  
    

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.
