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

- Source: https://support.icompaas.com/support/solutions/articles/62000234929-ensure-audit-logging-of-all-attempts-to-use-the-usermod-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 usermod command modifies user account properties. Recording both successful and unsuccessful attempts to use usermod is critical to detect unauthorized changes to user accounts and maintain system security.

Rationale:  
 Auditing all executions of the usermod command supports accountability and helps identify potential misuse or malicious activity.

Impact:  
 Pros:

-   Provides visibility into user account modifications.  
    
-   Supports forensic analysis and compliance.  
    

Cons:

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

Default Value:  
 Audit of usermod command usage is typically 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 usermod:

auditctl -l | grep usermod

Verify audit rules exist for tracking executions of usermod.  

### Implementation Plan:

Using Linux command line:

Add audit rules to log execution of usermod:

auditctl -w /usr/sbin/usermod -p x -k usermod-change

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 usermod audit rule if necessary:

auditctl -W /usr/sbin/usermod -p x -k usermod-change

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.
