What evidence do auditors commonly ask for on AC.L2-3.1.8 Unsuccessful Logon Attempts?

Configured lockout threshold, duration and reset settings; Policy stating the failed attempt limit and resulting action; Evidence of enforcement across all authentication paths including remote.

What is the most common gap auditors find on AC.L2-3.1.8?

Limit set in policy but not configured on all systems

CMMC 2.0 · Access Control

`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.

Source: CMMC 2.0, AC.L2-3.1.8. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Identity provider / directory

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Configured lockout threshold, duration and reset settings · Identity provider / directory
Evidence of enforcement across all authentication paths including remote · Identity provider / directory

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Policy stating the failed attempt limit and resulting action · Policy repository / GRC workspace

First move

Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.

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 sheet

AC.L2-3.1.7 Privileged Functions · AC.L2-3.1.9 Privacy & Security Notices