Security requirement
- a.Maintain a list of commonly-used, expected, or compromised passwords, and update the list [Organization-defined: 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: [Organization-defined: rules].
Discussion
Password-based authentication applies to passwords used in single-factor or multi-factor authentication. Long passwords or passphrases are preferable to shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish and enforce certain rules for password generation (e.g., minimum character length) under certain circumstances. For example, account recovery can occur when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof. Changing temporary passwords to permanent passwords immediately after system logon ensures that the necessary strength of the authentication mechanism is implemented at the earliest opportunity and reduces susceptibility to authenticator compromises. Long passwords and passphrases can be used to increase the complexity of passwords.
Tailoring decisions required
Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.
Implementation perspective
Treat Password Management as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to identity proofing, authentication strength, authenticator lifecycle, and resistance to credential compromise.
- Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
- Resolve every organization-defined parameter through an approved governance and tailoring process.
- Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
- Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
- Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.
Questions to ask
- Which CUI assets, data flows, users, and services are protected by this requirement?
- Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
- Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
- What change, incident, or threshold should trigger reassessment?
Evidence and validation
- identity proofing records
- authenticator issuance and revocation logs
- MFA and federation configuration
- credential inventories and rotation evidence
Common failure patterns
- MFA applied only to interactive users
- service credentials without ownership or rotation
- weak recovery paths that bypass strong authentication
- federated trust not reviewed after partner changes
Assessment objectives and methods
Assessment objectives (8)
- a.
a list of commonly used, expected, or compromised passwords is maintained.
- a.
a list of commonly used, expected, or compromised passwords is updated [Organization-defined: frequency].
- a.
a list of commonly used, expected, or compromised passwords is updated when organizational passwords are suspected to have been compromised.
- b.
passwords are verified not to be found on the list of commonly used, expected, or compromised passwords when they are created or updated by users.
- c.
passwords are only transmitted over cryptographically protected channels.
- d.
passwords are stored in a cryptographically protected form.
- e.
a new password is selected upon first use after account recovery.
- f.
the following composition and complexity rules for passwords are enforced: [Organization-defined: rules].
Examine
- identification and authentication policy and procedures
- password policy
- procedures for authenticator management
- system design documentation
- system configuration settings
- password configurations
- system security plan
- other relevant documents or records
Interview
- personnel with authenticator management responsibilities
- personnel with information security responsibilities
- system developers
- system administrators
Test
- mechanisms for supporting or implementing a password-based authenticator management capability
Source NIST SP 800-53 controls
These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.
Authoritative sources
- NIST SP 800-171 Revision 3 official publication ↗
- NIST SP 800-171A Revision 3 official publication ↗
- NIST OSCAL Content release used for this import ↗
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.