# Ensure pam_faillock Module Is Enabled

- Source: https://support.icompaas.com/support/solutions/articles/62000235524-ensure-pam-faillock-module-is-enabled
- 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 pam\_faillock module provides authentication failure tracking and account locking functionality. Enabling this module helps protect against brute-force attacks by locking user accounts after a configurable number of failed login attempts.

**Rationale:** Using pam\_faillock enhances security by limiting repeated failed login attempts, thus preventing unauthorized access via password guessing.

**Impact:** Pros:

-   Mitigates brute-force and credential stuffing attacks.  
    
-   Protects user accounts by locking after failed attempts.  
    

Cons:

-   May result in legitimate users being locked out if thresholds are too low.  
    

**Default Value:** The pam\_faillock module may not be enabled by default and requires configuration.

**Pre-requisites:**

-   Root or sudo privileges to modify PAM configuration files.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1.  Check PAM configuration files (e.g., /etc/pam.d/system-auth, /etc/pam.d/password-auth) for pam\_faillock usage:  
    
    grep pam\_faillock /etc/pam.d/system-auth /etc/pam.d/password-auth
    
2.  Verify that pam\_faillock is present and properly configured.
    

### **Implementation Plan:**

**Using Linux command line:**

1.  Edit PAM configuration files to enable pam\_faillock, for example, add:  
    
    auth required pam\_faillock.so preauth audit silent deny=5 unlock\_time=900  
    auth \[default=die\] pam\_faillock.so authfail audit deny=5 unlock\_time=900  
    account required pam\_faillock.so
    
2.  Save changes.  
    

### **Backout Plan:**

**Using Linux command line:**

1.  Remove or comment out pam\_faillock entries if necessary.
    
2.  Test authentication behavior after changes.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   pam\_faillock Manual  
    
-   [NIST SP 800-53 Revision 5 - AC-7  
    ](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#ac-7)

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