# Ensure Password Maximum Sequential Characters Is Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235457-ensure-password-maximum-sequential-characters-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 limits on the maximum number of sequential characters in passwords prevents users from choosing passwords with easily guessable sequences (e.g., “abcd”, “1234”), thereby strengthening password security.

**Rationale:** Restricting sequential characters reduces the risk of weak passwords vulnerable to pattern-based attacks and improves overall authentication security.

**Impact:** Pros:

-   Encourages stronger and less predictable passwords.  
    
-   Mitigates risks from common sequential patterns.  
    

Cons:

-   May increase user difficulty in creating passwords.  
    

**Default Value:** This setting is not always configured by default and requires explicit configuration.

**Pre-requisites:**

-   Root or sudo privileges to configure PAM modules such as pam\_pwquality.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Check /etc/security/pwquality.conf for maxsequence parameter which controls max allowed sequential characters:  
    
    grep maxsequence /etc/security/pwquality.conf
    
      
    
2.  Verify maxsequence is set appropriately (e.g., 3 or fewer).
    

### **Implementation Plan:**

**Using Linux command line:**

1.  Edit /etc/security/pwquality.conf to set maxsequence, for example:  
    
    maxsequence = 3
    
      
    
2.  Save the file and ensure PAM is configured to use pam\_pwquality.  
    

### **Backout Plan:**

**Using Linux command line:**

1.  Remove or adjust the maxsequence parameter if needed.
    
2.  Test password change functionality.  
    

**References:**

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   pwquality.conf 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.
