03.05.07 Password Management
What the standard requires
a. Maintain a list of commonly-used, expected, or compromised passwords, and update the list [frequency] and when organizational passwords are suspected to have been compromised. b. Verify that passwords are not found on the list of commonly used, expected, or compromised passwords when users create or update passwords. c. Transmit passwords only over cryptographically protected channels. d. Store passwords in a cryptographically protected form. e. Select a new password upon first use after account recovery. f. Enforce the following composition and complexity rules for passwords: [rules].
Quoted verbatim from NIST SP 800-171 Rev 3, which is in the public domain.
Cross-framework mappings
No cross-framework mapping is seeded for this control. That is stated rather than filled in: a mapping nobody authored is worse than a gap you can see.
Integrations that carry evidence for this family
These connectors produce data relevant to NIST SP 800-171 Revision 3’s Identification and Authentication family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.