Account lockout meaning, in plain words

Account lockout pauses login after repeated failures to slow guessing. How OWASP and NIST say to count and release it, and the risk of locking people out.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Account lockout is a mechanism that stops login for a while when failures continue. It is used to stop, by count, the brute-force attack in which passwords are tried at random again and again. OWASP describes it as a measure that refuses logins for a time after failures reach a set number.

How does account lockout work?

If you get a PIN wrong a few times, a cash card stops working for a while. This is the same idea. The site counts failures for each account, and when the limit is passed, it stops attempts on that account for a fixed time.

OWASP says failures should be counted against the account, not against the IP address of the source. If you count per IP address, an attacker can keep trying while changing addresses. Three items need deciding: the number of failures allowed, the period over which they are counted, and how long the lock lasts, and they must be balanced.

You can also lengthen the wait with each failure, rather than keeping the lock time fixed. NIST SP 800-63B-4 gives waiting longer as failures pile up as an example of an additional measure that reduces lock-outs. Brute-force attacks themselves are covered in brute-force attacks. For help with your login design, contact us.

Why does account lockout matter?

Without a limit on counts, password candidates can be tried endlessly. MITRE's CWE-307 classifies as a weakness the lack of measures against many failures in a short time.

A stopping mechanism, if used badly, causes trouble of its own. OWASP warns against its use in denial-of-service tricks that deliberately lock other people's accounts. NIST also sets consecutive failures at no more than 100 per authentication method, but that is a ceiling and a lower number is allowed. When designing, check these points.

  • Count failures per account.
  • Release automatically after a set time, or lengthen the wait in steps.
  • Even while locked, leave the real owner a way back through password reset.
  • Use multi-factor authentication as well.

OWASP positions multi-factor authentication as the best defense against most password-related attacks. It says CAPTCHA is a way to layer defenses, not something that stops attacks alone.

Related terms

Frequently asked questions

Will lockout stop unauthorized login?

It is not enough alone. OWASP calls multi-factor authentication the best defense and treats CAPTCHA as a way to layer defenses. Lockout does the job of stopping attempts by count, and is used together with these.

How does the locked-out person get back in?

OWASP says the password reset procedure should still work for a forgotten password while an account is locked. Decide how to release a lock so the real owner is not shut out for long.

Next step

The methods and countermeasures for brute-force attacks are in brute-force attacks. The free URL check shows only what is visible from outside, and to discuss how your login should be designed, contact us.

Frequently asked questions

Will lockout stop unauthorized login?

It is not enough alone. OWASP calls multi-factor authentication the best defense and treats CAPTCHA as a way to layer defenses. Lockout does the job of stopping attempts by count, and is used together with these.

How does the locked-out person get back in?

OWASP says the password reset procedure should still work for a forgotten password while an account is locked. Decide how to release a lock so the real owner is not shut out for long.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.