Security requirement
Obscure feedback of authentication information during the authentication process.
Discussion
Authentication feedback does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For example, for desktop or notebook systems with relatively large monitors, the threat may be significant (commonly referred to as shoulder surfing). For mobile devices with small displays, this threat may be less significant and is balanced against the increased likelihood of input errors due to small keyboards. Therefore, the means of obscuring authenticator feedback is selected accordingly. Obscuring feedback includes displaying asterisks when users type passwords into input devices or displaying feedback for a limited time before fully obscuring it.
Implementation perspective
Treat Authentication Feedback 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 (1)
- SR-03.5.11.
feedback of authentication information during the authentication process is obscured.
Examine
- identification and authentication policy and procedures
- procedures for authenticator feedback
- system design documentation
- system configuration settings
- system audit records
- system security plan
- other relevant documents or records
Interview
- personnel with information security responsibilities
- system developers
- system administrators
Test
- mechanisms for supporting or implementing the obscuring of feedback of authentication information during authentication
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.