# Ensure Enforce Prohibition of Default Passwords on Systems and Applications

- Source: https://support.icompaas.com/support/solutions/articles/62000235033-ensure-enforce-prohibition-of-default-passwords-on-systems-and-applications
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS GitHub Benchmark v1.0.0](https://support.icompaas.com/support/solutions/62000112695) › [CIS GitHub Benchmark v1.0.0](https://support.icompaas.com/support/solutions/folders/62000169264)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:**  
Level 1

**Description:**  
Default passwords on systems, devices, applications, and services must be changed before deployment or use. Use of default credentials poses a significant security risk, as they are widely known and can be exploited by attackers to gain unauthorized access.

**Rationale:**  
Changing default passwords is a fundamental security measure to prevent unauthorized access and potential compromise of systems. It enforces secure authentication practices and reduces the attack surface.

**Impact:****Pros:**

-   Mitigates risk of unauthorized access due to known default credentials.  
      
    
-   Strengthens overall system and application security.  
      
    
-   Supports compliance with security policies and regulatory standards.  
      
    

**Cons:**

-   Requires administrative effort to change and manage passwords.  
      
    
-   Risk of weak password choices if not properly managed.  
      
    

**Default value:**  
Many systems ship with default passwords that are unchanged, exposing them to high risk.

**Audit:**  
Review system and application configurations to detect any use of default passwords. Use automated tools where possible to identify default credentials.

**Remediation:**  
Establish policies mandating password changes before deployment. Implement strong password policies and password management solutions. Train administrators on secure credential management.

**References:**

1.  CIS Controls v8, Control 4 - Secure Configuration of Enterprise Assets and Software: [https://www.cisecurity.org/controls/secure-configuration-of-enterprise-assets-and-software/](https://www.cisecurity.org/controls/secure-configuration-of-enterprise-assets-and-software/)
    
2.  NIST SP 800-63B Digital Identity Guidelines: [https://pages.nist.gov/800-63-3/sp800-63b.html](https://pages.nist.gov/800-63-3/sp800-63b.html)
    
3.  OWASP Authentication Cheat Sheet: [https://cheatsheetseries.owasp.org/cheatsheets/Authentication\_Cheat\_Sheet.html](https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.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.