AC.L2-3.1.8 Unsuccessful Logon Attempts
Cap the number of consecutive failed logon attempts allowed and take a defined action, such as account lockout, once that limit is reached.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Evidence of enforcement across all authentication paths including remote · Identity provider / directory
governing documentDocuments that govern the control
- Configured lockout threshold, duration and reset settings · Policy repository / GRC workspace
- Policy stating the failed attempt limit and resulting action · 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
- Limit set in policy but not configured on all systems
- Remote and application logons exempt from lockout
- Lockout thresholds so high they never trigger
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 sheetAC.L2-3.1.7 Privileged Functions · AC.L2-3.1.9 Privacy & Security Notices