# Ensure Inactive Password Lock Is 30 Days or Less

- Source: https://support.icompaas.com/support/solutions/articles/62000235472-ensure-inactive-password-lock-is-30-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:**  
 The inactive password lock setting defines the number of days after a password expires before the account is locked. Setting this value to 30 days or less ensures timely disabling of inactive accounts, reducing the risk of unauthorized access.

**Rationale:** Enforcing a short inactive password lock period limits the window in which expired accounts can be exploited, enhancing system security by disabling stale accounts promptly.

**Impact:** Pros:

-   Reduces risk from unused or compromised accounts.  
    
-   Supports compliance with account management policies.  
    

Cons:

-   May inadvertently lock accounts if users do not update passwords timely.  
    

**Default Value:** Inactive password lock period may vary and is sometimes not configured.

**Pre-requisites:**

-   Root or sudo privileges to configure account aging policies.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1\. Check current inactive password lock settings for a user:  

chage -l <username> | grep "Password inactive"

2\. Review global defaults in /etc/login.defs if applicable:

grep INACTIVE /etc/login.defs

###   
**Implementation Plan:**

**Using Linux command line:**

1\. Set the inactive password lock period globally in /etc/login.defs:  

vi /etc/login.defs

2\. Update or add the line:  

INACTIVE 30

3\. For individual users, use chage:  

chage -I 30 <username>

4\. Verify settings:  

chage -l <username>

###   
**Backout Plan:**

**Using Linux command line:**

1.  Increase the inactive password lock period if necessary by modifying /etc/login.defs and/or using chage.  
    
2.  Verify changes.  
    

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