IA.L2-3.5.11 Obscure Feedback
Obscure authentication feedback during entry so credentials cannot be read from the screen.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Configuration or screenshots showing masked credential entry · Identity provider / directory
- Evidence error messages do not disclose credential details · Identity provider / directory
governing documentDocuments that govern the control
- Coverage across systems, applications and mobile interfaces · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Masking present in some applications only
- Error feedback reveals whether the username or password was wrong
- Show password features enabled by default
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIA.L2-3.5.10 Cryptographically-Protected Passwords · IR.L2-3.6.1 Incident Handling