CMMC 2.0
Identification and Authentication

CMMC 2.0 IA.L2-3.5.10: Cryptographically-Protected Passwords

Store and transmit passwords only in cryptographically protected form.

What else in your programme already covers this

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

FedRAMP High · 3 controls

  • IA-5(1) Password-Based Authentication
  • IA-5(6) Protection of Authenticators
  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators. Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage

FedRAMP Moderate · 3 controls

  • IA-5(1) Password-Based Authentication
  • IA-5(6) Protection of Authenticators
  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators. Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage

PCI DSS 4.0 · 3 controls

  • 8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components
  • 9.2.4 Consoles in sensitive areas locked when not in use
  • 8.6.2 Passwords/passphrases for any application and system accounts that can be used for interactive login are not hard coded in scripts, configuration/property files, or bespoke and custom source code
  • ASBv3-DP-6 Use a secure key management process
  • ASBv3-IM-8 Restrict the exposure of credential and secrets

C5 (Germany) · 2 controls

  • C5-IDM-08 Confidentiality of authentication information
  • C5-PSS-07 Confidentiality of Authentication Information

ISO 27001:2022 · 2 controls

  • 5.17 Authentication information
  • 8.24 Use of cryptography

ISO 27701:2019 · 2 controls

  • 6.6.3 User responsibilities
  • 6.7.1 Cryptographic controls
  • NIST-CSF-PR.AA-04 Identity assertions are protected, conveyed, and verified
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • ASD37-23 Protect authentication credentials (Excellent)

CIS Controls v8 · 1 control

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 5.17 Authentication information

NIST SP 800-172 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets

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 Identification and Authentication

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 IA.L2-3.5.10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 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. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

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