Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
IAM - Identity & Access Management

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IAM-15: Passwords Management

Manage passwords securely across their lifecycle through defined and evaluated processes and technical measures.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 47 controls across 22 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 9 controls

  • 8.3.11 8.3.11 Tokens, smart cards and certificates individually assigned
  • 8.3.2 8.3.2 Authentication factors unreadable with strong cryptography
  • 8.3.3 8.3.3 Identity verified before factor changes
  • 8.3.5 8.3.5 Initial and reset passwords unique and changed
  • 8.3.7 8.3.7 No reuse of last four passwords
  • 8.3.9 8.3.9 Single-factor passwords changed every 90 days or dynamic analysis
  • 9.2.4 9.2.4 Locking of consoles in sensitive areas
  • 8.6.2 8.6.2 No hard-coded passwords for interactive system accounts
  • 8.6.3 8.6.3 System account passwords protected against misuse

FedRAMP High · 4 controls

  • IA-5 Authenticator Management
  • IA-5(1) Password-Based Authentication
  • IA-5(6) Protection of Authenticators
  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))

FedRAMP Moderate · 4 controls

  • IA-5 Authenticator Management
  • IA-5(1) Password-Based Authentication
  • IA-5(6) Protection of Authenticators
  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))
  • ANSSI-HYG-10 Define and Verify Password Selection and Sizing Rules
  • ANSSI-HYG-11 Protect Passwords Stored on Systems
  • ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services

CMMC 2.0 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

UK Cyber Essentials · 3 controls

  • CE-SC.2 Change Default Passwords on Devices and Software
  • CE-SC.5 Password-Based Authentication Quality
  • CE-SC.8 Process for Compromised Passwords
  • ASD37-21 Disable local administrator accounts (Excellent)
  • ASD37-23 Protect authentication credentials (Excellent)
  • ASBv3-IM-8 Restrict the exposure of credential and secrets
  • IM-3 Manage application identities securely and automatically

C5 (Germany) · 2 controls

  • C5-IDM-08 Confidentiality of authentication information
  • C5-PSS-07 Confidentiality of Authentication Information
  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

CIS Controls v8 · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.17 Authentication information

ISO 27002:2022 · 1 control

  • 5.17 Authentication information

ISO 27701:2019 · 1 control

  • 6.6.3 User responsibilities
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-172 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in IAM - Identity & Access Management

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IAM-15 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 47 it maps to, and the evidence behind each claim, over MCP and REST.