# Ensure Password Expiration Is 365 Days or Less

- Source: https://support.icompaas.com/support/solutions/articles/62000235468-ensure-password-expiration-is-365-days-or-less
- 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:**  
 Setting a maximum password age of 365 days or less enforces regular password changes, reducing the risk of compromised credentials being used over extended periods.

**Rationale:** Regular password expiration mitigates the risk of long-term password compromise and encourages better password hygiene among users.

**Impact:** Pros:

-   Limits the time a compromised password is valid.  
    
-   Encourages users to update passwords regularly.  
    

Cons:

-   May increase helpdesk support due to password resets.  
    
-   Frequent changes can lead to weaker passwords if users choose predictable patterns.  
    

**Default Value:** Password expiration policies vary by system and may not enforce a maximum age by default.

**Pre-requisites:**

-   Root or sudo privileges to configure password aging policies.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1\. Check current password expiration for users using chage:  

chage -l <username>

2\. Review /etc/login.defs for default maximum password age:

grep PASS\_MAX\_DAYS /etc/login.defs

###   
**Implementation Plan:**

**Using Linux command line:**

1\. Set maximum password age to 365 days or less globally in /etc/login.defs:  

vi /etc/login.defs

2\. Update or add the line:  

PASS\_MAX\_DAYS 365

3\. For specific users, update with chage:  

chage -M 365 <username>

4\. Verify settings  

chage -l <username>

### **  
Backout Plan:**

**Using Linux command line:**

1.  Increase password expiration period if necessary by modifying /etc/login.defs and/or using chage.  
    
2.  Verify changes take effect.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   chage Manual  
    
-   [NIST SP 800-63B - Digital Identity Guidelines  
    ](https://pages.nist.gov/800-63-3/sp800-63b.html)

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