# Ensure Proper Permissions on /etc/passwd File

- Source: https://support.icompaas.com/support/solutions/articles/62000235427-ensure-proper-permissions-on-etc-passwd-file
- 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:  
 The /etc/passwd file contains essential user account information. While this file does not store password hashes (which reside in /etc/shadow), improper permissions on /etc/passwd can allow unauthorized users to read sensitive system information.

Rationale:  
 Setting secure permissions on /etc/passwd helps prevent unauthorized access to user account information and supports overall system security.

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

-   Protects user account information from unauthorized reading or modification.  
    
-   Helps maintain system integrity and user privacy.  
    

**Cons:**

-   Permissions must allow read access for normal system operation by all users.  
    

Default Value:  
 Typically, /etc/passwd permissions are set to 644 with ownership by root:root.

Pre-requisites:

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

Remediation:

### Test Plan:

Using Linux command line:

1.  Check current permissions of /etc/passwd:
    
    ls -l /etc/passwd
    
2.  Verify ownership is root:root and permissions are set to 644.  
    

### Implementation Plan:

Using Linux command line:

1.  Set ownership to root:
    
    chown root:root /etc/passwd
    
2.  Set permissions to 644:
    
    chmod 644 /etc/passwd
    
3.  Verify changes:
    
    ls -l /etc/passwd
    

### Backout Plan:

Using Linux command line:

1.  Restore previous permissions and ownership from backup if necessary.  
    
2.  Confirm system utilities operate correctly after changes.  
    

References:

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