IA-6 Authentication feedback
Requires feedback shown during authentication to be obscured so that an observer or an attacker cannot harvest authentication information from what the system displays or returns.
4
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
- Screenshots or configuration showing masked credential entry · Identity provider / directory
- Test evidence that responses do not disclose whether an account exists · Identity provider / directory
governing documentDocuments that govern the control
- Error message specification showing failures do not reveal which factor was wrong · Policy repository / GRC workspace
- Coverage across web, mobile, console and recovery flows · 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
- Error messages distinguish unknown user from wrong password and enable enumeration
- Credentials echoed in console or terminal sessions during administration
- Recovery and password reset flows leak whether an address is registered
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-5 Authenticator management · IA-7 Cryptographic module authentication