# Ensure Password History Remember Is Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235460-ensure-password-history-remember-is-configured
- 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:**  
 Configuring password history remember enforces that users cannot reuse a specified number of their previous passwords. This policy strengthens password security by preventing password recycling.

**Rationale:** Enforcing password history reduces the risk of compromised accounts due to reused or predictable passwords, enhancing overall authentication security.

**Impact:** Pros:

-   Prevents password reuse, encouraging stronger and more unique passwords.  
    
-   Supports compliance with security standards and best practices.  
    

Cons:

-   Users may face difficulty recalling unique passwords, possibly increasing support requests.  
    

**Default Value:** Password history enforcement may not be configured by default.

**Pre-requisites:**

-   Root or sudo privileges to modify PAM configuration files.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Verify PAM configuration includes password history settings:  
    
    grep pam\_pwhistory /etc/pam.d/system-auth  
    grep pam\_pwhistory /etc/pam.d/common-password
    
      
    
2.  Confirm presence of remember=<number> option (e.g., remember=5).  
    

### **Implementation Plan:**

**Using Linux command line:**

1\. Edit the relevant PAM configuration file (e.g., /etc/pam.d/system-auth or /etc/pam.d/common-password):  

vi /etc/pam.d/system-auth

2\. Add or update the line to include the remember parameter:

password required pam\_pwhistory.so use\_authok remember=5 enforce\_for\_root

3\. Save the file.  

### **Backout Plan:**

**Using Linux command line:**

1.  Remove or modify the remember parameter if necessary.
    
2.  Test password changes to ensure proper functionality.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   pam\_pwhistory Documentation  
    
-   [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.
