# Ensure Audit Logging of All Attempts to Use the chcon Command

- Source: https://support.icompaas.com/support/solutions/articles/62000234922-ensure-audit-logging-of-all-attempts-to-use-the-chcon-command
- 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 chcon command is used to change SELinux security contexts on files and processes. Recording both successful and unsuccessful attempts to use chcon is critical to detect unauthorized or suspicious modifications to security labels.

Rationale:  
 Auditing all uses of chcon helps maintain SELinux policy integrity by providing visibility into security context changes and potential misuse.

Impact:  
 Pros:

-   Provides comprehensive monitoring of SELinux context modifications.  
    
-   Supports detection of policy violations or attacks targeting SELinux settings.  
    

Cons:

-   May increase audit log volume; requires effective log management.  
    

Default Value:  
 Audit of chcon command usage is often not enabled by default.

Pre-requisites:

-   Root or sudo privileges to configure audit rules.  
    

Remediation:

### Test Plan:

Using Linux command line:

Check current audit rules for chcon

auditctl -l | grep chcon

1.  Verify audit rules exist for tracking chcon execution.
    

### Implementation Plan:

Using Linux command line:

Add audit rules to log both successful and unsuccessful executions of chcon:

auditctl -w /usr/bin/chcon -p x -k chcon-change

1.  Persist audit rules by adding the above line to /etc/audit/rules.d/audit.rules.  
    

### Backout Plan:

Using Linux command line:

Remove or disable the chcon audit rule if needed:

auditctl -W /usr/bin/chcon -p x -k chcon-change

1.  Reload audit daemon configuration.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   SELinux Audit  
    
-   [Linux Audit Framework  
    ](https://linux-audit.com/)

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