Lock out accounts after too many bad password attempts.
What it actually means
Limit unsuccessful logon attempts to slow down password-guessing and brute-force attacks. Set an account-lockout threshold and lockout duration across your systems — workstations, servers, VPN, and cloud identity.
Pass or fail — an assessor needs a "yes" to each
- Is an account-lockout threshold enforced after a defined number of failed attempts?
- Does it apply across systems, including remote access and cloud identity?
What to have ready
- Lockout policy configuration (GPO / Entra ID / etc.)
- Settings showing the threshold and duration
Where teams trip up
- No lockout on cloud or VPN logins
- A threshold set so high it's meaningless
See where this control puts your score
Run all 110 requirements free in about 10 minutes — or draft your SSP language for this control. No signup.
Calculate your SPRS score →Draft your SSP language →Connected requirements
More in Access Control (3.1)
3.1.1 — Limit who (and what) can get in3.1.2 — Limit what users can do3.1.3 — Control the flow of CUI3.1.4 — Separate duties3.1.5 — Least privilege (especially for admins)3.1.6 — Use non-privileged accounts for routine work3.1.7 — Restrict and log privileged functions3.1.9 — Show privacy and security notices3.1.10 — Lock idle screens3.1.11 — End sessions automatically3.1.12 — Monitor and control remote access3.1.13 — Encrypt remote access sessions3.1.14 — Funnel remote access through managed points3.1.15 — Authorize privileged remote actions3.1.16 — Authorize wireless access first3.1.17 — Protect wireless with authentication + encryption3.1.18 — Control mobile device connections3.1.19 — Encrypt CUI on mobile devices3.1.20 — Control connections to external systems3.1.21 — Limit portable storage on external systems3.1.22 — Control what goes on public systems