# Ensure Audit Logging of Privileged Command Usage

- Source: https://support.icompaas.com/support/solutions/articles/62000234893-ensure-audit-logging-of-privileged-command-usage
- 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:  
 Privileged commands allow users to perform actions with elevated privileges, potentially impacting system security. Collecting audit logs of privileged command usage helps monitor and detect unauthorized or malicious activities.

Rationale:  
 Auditing privileged command execution provides visibility into administrative actions, enabling accountability and timely detection of misuse or compromise.

Impact:  
 Pros:

-   Enhances security monitoring of privileged operations.  
    
-   Supports forensic investigations and compliance requirements.  
    

Cons:

-   May generate a high volume of audit logs; requires effective log management.  
    

Default Value:  
 Audit logging for privileged commands may not be enabled by default.

Pre-requisites:

-   Root or sudo privileges to configure audit rules.  
    

Remediation:

### Test Plan:

Using Linux command line:

Check existing audit rules for privileged command execution:

auditctl -l | grep -E '/bin/su|/bin/sudo|/usr/bin/sudo'

1.  Verify audit rules exist for tracking execution of privileged commands.  
    

### Implementation Plan:

Using Linux command line:

Add audit rules to monitor privileged commands, for example:

auditctl -w /bin/su -p x -k privileged-command  
auditctl -w /bin/sudo -p x -k privileged-command  
auditctl -w /usr/bin/sudo -p x -k privileged-command

1.  Persist audit rules by adding them to /etc/audit/rules.d/audit.rules.  
    

### Backout Plan:

Using Linux command line:

Remove audit rules for privileged commands if necessary:

auditctl -W /bin/su -p x -k privileged-command  
auditctl -W /bin/sudo -p x -k privileged-command  
auditctl -W /usr/bin/sudo -p x -k privileged-command  
auditctl -D -k privileged-command

1.  Reload audit daemon configuration.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   [Linux Audit Framework  
    ](https://linux-audit.com/)
    
-   [NIST SP 800-53 Revision 5 - AU-6  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#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.