Account lockout is a security control that disables sign-in to an account after a defined number of consecutive failed authentication attempts, either for a fixed period or until an administrator or the user restores access. In identity & access management within cybersecurity, it is one of the oldest defenses against online password guessing, because it caps how many guesses an attacker can make against a single account.
The control is simple to describe but difficult to tune. A threshold that is too strict turns lockout into a denial-of-service weapon against legitimate users, while a threshold that is too loose provides little protection. Modern guidance therefore treats lockout as one layer among several, combined with throttling, MFA and anomaly detection, rather than as a standalone safeguard.
How account lockout works
An account lockout mechanism counts failed sign-in attempts per account and blocks further attempts once the count reaches a lockout threshold. The authentication service stores a counter, a timestamp of the first failure and, once triggered, the time at which the lock expires.
Three parameters define the behavior. The threshold sets how many failures are tolerated, the observation window (sometimes called the reset counter interval) defines how long failures are remembered, and the lockout duration decides how long the account stays blocked. A successful sign-in normally resets the counter to zero.
The table below summarizes the core parameters and the values commonly seen in enterprise directories and web applications.
| Parameter | Typical range | What it controls |
|---|---|---|
| Lockout threshold | 5 to 10 failures | How many wrong attempts trigger the lock |
| Observation window | 15 to 30 minutes | How long failed attempts are counted |
| Lockout duration | 15 minutes to permanent | How long the account remains blocked |
| Counter reset | On success or window expiry | When the failure count returns to zero |
| Unlock method | Timer, self-service, help desk | Who or what restores access |
Where the counter lives matters. In a centralized directory such as Active Directory, the lock applies to every service that authenticates against it. In federated setups, the identity provider usually enforces lockout, so applications using SSO through SAML or OpenID Connect inherit its policy rather than keeping their own counters.
Types of lockout policies
Lockout policies differ mainly in how access is restored and how aggressively attempts are slowed. Choosing a type is a balance between security, user friction and support cost.
| Policy type | Behavior | Best suited for |
|---|---|---|
| Time-based lockout | Unlocks automatically after a set period | General workforce and consumer accounts |
| Permanent lockout | Requires administrator action to unlock | Privileged and high-value accounts |
| Progressive delay | Wait time grows with each failure | Public web applications |
| Soft lockout | Requires extra verification such as a CAPTCHA | Consumer services with large user bases |
| Risk-based lockout | Blocks only suspicious attempts by context | Organizations with mature identity platforms |
Progressive delay, also called exponential backoff, is often preferred to hard lockout because it slows automated guessing without fully denying the real user. Risk-based approaches go further: they evaluate source IP reputation, device fingerprint and geolocation, and lock only the suspicious session while allowing the recognized device to continue.
Account lockout compared with related controls
Account lockout is one of several rate-limiting defenses, and it is frequently confused with throttling and with session expiry. The comparison below clarifies what each control protects and where it falls short.
| Control | Scope | Main strength | Main weakness |
|---|---|---|---|
| Account lockout | Per account | Caps guesses on one account | Enables targeted denial of service |
| IP throttling | Per source address | Slows a single attacking host | Bypassed by distributed botnets |
| MFA | Per sign-in | Stops use of stolen passwords | Push fatigue and phishing risks |
| Token expiration | Per session | Limits reuse of stolen tokens | Does not limit password guessing |
| Breached password screening | Per credential | Blocks known leaked passwords | Cannot detect unknown leaks |
The key insight is that lockout protects individual accounts against brute force, but it does little against password spraying, where an attacker tries one or two common passwords across thousands of accounts and stays below every per-account threshold. Detecting spraying requires aggregate monitoring across accounts, typically in the identity provider or a security information and event management platform.
Configuring lockout in practice
Effective configuration starts from the threat model and the strength of other controls. Current NIST SP 800-63B guidance requires verifiers to limit consecutive failed attempts to no more than 100 on a single account, which is far looser than traditional values, because it assumes rate limiting and strong password screening are also in place.
Older baselines often recommended thresholds of three to five attempts, which generated large help desk volumes from users mistyping passwords. Many organizations now use ten failures with a 15-minute automatic unlock for standard accounts and stricter rules only for privileged identities.
| Situation | Recommended approach | Reason |
|---|---|---|
| Workforce accounts with MFA | 10 failures, 15-minute unlock | MFA already blocks most password misuse |
| Administrator accounts | Low threshold, manual unlock | Compromise impact is severe |
| Public consumer login | Progressive delay plus CAPTCHA | Avoids mass lockout by attackers |
| Service accounts | Exclude and monitor instead | Lockout can stop critical systems |
| Passwordless sign-in | Rate limit the fallback path | Passkeys resist guessing by design |
- Return the same error message for a wrong password and a locked account to avoid revealing account state.
- Apply lockout to every authentication path, including legacy protocols, APIs and password reset flows.
- Log lockout events and alert on unusual volumes, which often indicate an active attack.
- Offer self-service unlock protected by a second factor to reduce help desk load.
Limitations, risks and common mistakes
The most serious limitation is that lockout can be turned against the organization. An attacker who knows usernames can deliberately enter wrong passwords to lock out executives, help desk staff or an entire user population, creating a denial-of-service condition without ever breaching an account.
Another frequent failure is inconsistent enforcement. Legacy protocols such as basic authentication over IMAP or older remote access gateways sometimes bypass the lockout counter entirely, giving attackers an unlimited guessing channel. Cached credentials on mobile devices can also produce repeated lockouts after a password change, because the old password keeps being submitted in the background.
| Symptom | Likely cause | Fix |
|---|---|---|
| Repeated lockouts after password change | Stale credentials on a device | Find the source in logs and update it |
| Many accounts locked at once | Malicious lockout or spraying | Block source and enable risk-based rules |
| Attack succeeds without lockouts | Legacy protocol bypass | Disable legacy authentication |
| Username enumeration possible | Distinct locked-account message | Use one generic error message |
Finally, lockout does nothing against credential stuffing with correct passwords or against phishing that captures valid credentials. Organizations that rely on lockout alone often overestimate their protection; MFA, passkeys based on FIDO2 and breached password checks address the threats that lockout cannot.
A non-technical view
Account lockout works like a bank card that is swallowed by the cash machine after too many wrong PIN entries. The system assumes that someone who keeps guessing is probably not the owner, so it stops accepting attempts for a while.
The difficulty is finding the right balance. If the lock is too strict, honest people who mistype their password get stuck and must call for help. If it is too lenient, a stranger can keep guessing. The main takeaway is that lockout is a useful safety catch, but it works best together with a second sign-in step such as a code on your phone.
A concrete example
A regional hospital with about 4,000 staff accounts originally locked accounts after three failed attempts with manual unlock. Nurses who changed passwords often stayed signed in on shared workstations and phones, and the old passwords triggered lockouts several times a day. The help desk logged hundreds of unlock tickets each month, and clinicians sometimes lost access during shifts.
The security team moved to ten failures within 15 minutes with automatic unlock, required MFA for all remote access and disabled legacy mail protocols. They also set alerts for more than 50 lockouts per hour across the directory. Unlock tickets fell by roughly 80 percent, and a later password spraying attempt was detected through the aggregate alert even though no single account reached its threshold.