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