- Verify internally built and kiosk applications rather than assuming; custom UIs are where secrets get echoed.
- Review error messages and password-reset flows for username enumeration while examining the same screens.
03.05.11OFFICIAL TITLEPENDING NIST SME REVIEW
03.05.11 — Authentication Feedback
03.05 Identification and Authentication · NIST SP 800-171 Rev. 3
Independent summary of the official requirement
Requires obscuring the feedback of authentication information during the authentication process to protect it from possible exploitation or use by unauthorized individuals.
Rev. 3 requirement text is multi-part and parameterized with organization-defined values, so this site summarizes rather than reproduces it. The summary is independent — read the official publication for the binding wording.
NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
Password fields show dots, and error messages do not reveal which half of a credential pair was wrong. This is default behavior on mainstream platforms — the check that matters is custom applications and shop-floor HMI screens.
Mapped practices
Brilliant at the Basics practices that support this requirement
No practice maps to this requirement — deliberately.
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Doing the work
Implementation considerations and evidence
- A dated check of authentication screens across in-scope applications, including custom UIs
- Remediation records for any screen found echoing authentication information
Artifacts
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
The other revision
Where this came from in Rev. 2
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |