# Ensure Strong Password Hashing Algorithm Is Configured

- Source: https://support.icompaas.com/support/solutions/articles/62000235467-ensure-strong-password-hashing-algorithm-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 a strong password hashing algorithm (e.g., SHA-512) strengthens password storage security by making it more resistant to brute-force and dictionary attacks. This reduces the likelihood of password compromise.

**Rationale:** Using robust hashing algorithms protects stored passwords by increasing computational effort required for cracking, thereby enhancing overall system security.

**Impact:** Pros:

-   Enhances password security.  
    
-   Supports compliance with security best practices and standards.  
    

Cons:

-   May slightly increase CPU load during authentication.  
    

**Default Value:** Many modern Linux systems use SHA-512 or stronger hashing by default but this should be verified.

**Pre-requisites:**

-   Root or sudo privileges to modify password hashing configurations.  
    

**Remediation:**

### **Test Plan:**

**Using Linux command line:**

1\. Check the current password hashing algorithm in /etc/login.defs or PAM configuration:

grep ENCRYPT\_METHOD /etc/login.defs

2\. Verify the hashing algorithm is set to SHA512 or stronger.

### **Implementation Plan:**

**Using Linux command line:**

1\. Edit /etc/login.defs to set strong hashing algorithm:

vi /etc/login.defs

2\. Set or update the following line:  

ENCRYPT\_METHOD SHA512

3\. Save the file.  

### **Backout Plan:**

**Using Linux command line:**

1.  Revert changes in /etc/login.defs if necessary.
    
2.  Test password changes to verify behavior.  
    

**References:**

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