# Ensure Proper Permissions on /etc/shadow File

- Source: https://support.icompaas.com/support/solutions/articles/62000235420-ensure-proper-permissions-on-etc-shadow-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/shadow file contains users’ encrypted password information and related authentication data. Improper permissions on this file can expose sensitive data to unauthorized users, increasing the risk of credential compromise and privilege escalation.

Rationale: Securing permissions on /etc/shadow ensures that only privileged users (typically root) can access sensitive authentication information, thereby maintaining system security.

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

-   Protects sensitive password hashes from unauthorized access.  
    
-   Enhances overall system authentication security.  
    

**Cons:**

-   Overly restrictive permissions might affect system utilities that require access (rare).  
    

Default Value:  
 Most Linux distributions set secure default permissions on /etc/shadow, but verification is necessary.

Pre-requisites:

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

Remediation:

### Test Plan:

Using Linux command line:

1.  Check current permissions and ownership of /etc/shadow:
    
    ls -l /etc/shadow
    
2.  Confirm the file is owned by root and permissions are set to 600 or more restrictive.
    

### Implementation Plan:

Using Linux command line:

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

### Backout Plan:

Using Linux command line:

1.  Restore previous permissions and ownership from backups if needed.  
    
2.  Test system utilities for proper functioning.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   [NIST SP 800-53 Revision 5 - IA-5  
      
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#ia-5)

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