aoitcloud

Guides and How Tos

Brute Force Attacks Explained (and Why Lockout Policies Matter)

What a brute force attack is, how credential stuffing differs, and why lockout policies, rate limiting, and 2FA together make accounts much harder to crack.

20 November 2026 4 min read

A brute force attack is one of the oldest tricks in the book: rather than exploiting a clever vulnerability, the attacker simply tries lots of passwords until one works. It sounds crude, and in some sense it is, but it remains a common way accounts get compromised, largely because so many defences against it are still missing on ordinary logins. Closing those gaps is exactly what our website security service is designed to do before an attacker gets anywhere close.

What a brute force attack actually is

A brute force attack systematically tries password guesses against one or more accounts, with no particular knowledge of the correct answer. This can mean working through every possible combination of characters, but in practice attackers are smarter than that. They typically start with dictionaries of common passwords, known patterns (adding a year or an exclamation mark to a common word, for example), and rules derived from how real people tend to choose passwords. Automated tools can attempt thousands of login combinations per minute against a login form, an SSH service, or an API, unless something stops them.

Credential stuffing: a related but different technique

Credential stuffing is often grouped alongside brute forcing, and OWASP does classify it as a subset of brute force attacks, but it works on a different principle. Rather than guessing, credential stuffing takes username and password pairs that have already been exposed in a data breach on one site, and tries them against other, unrelated sites. Because a large proportion of people reuse the same password across multiple accounts, a breach at one company can lead directly to account takeovers on services that were never breached themselves.

The practical difference matters: a brute force attack is a guessing game with no prior information, while credential stuffing uses real, previously valid credentials, which makes each attempt far more likely to succeed. This is precisely why reusing passwords across sites is so risky, a breach anywhere in your password’s history can compromise accounts everywhere else you have used it.

Why lockout policies and rate limiting slow attackers down

Both brute force and credential stuffing attacks depend on being able to make a large number of login attempts quickly. Two related defences directly target that assumption.

  • Account lockout policies temporarily or permanently disable a login after a set number of failed attempts, for example locking an account for 15 minutes after five incorrect passwords. This turns an attack that might have tried thousands of passwords per hour into one limited to a handful.
  • Rate limiting caps how many login attempts can come from a single IP address or client within a given time window, regardless of which account is being targeted. This is particularly useful against credential stuffing, where an attacker may be trying many different accounts rather than repeatedly hitting one.

Neither approach makes an account literally unbreakable, but both change the economics of the attack. An attacker who can only try a handful of passwords every 15 minutes needs an impractical amount of time to get through even a modest list of guesses, which pushes most automated attacks to move on to easier targets. Ongoing website monitoring also makes it easier to spot that kind of sustained attempt as it’s happening, rather than only after an account has already been compromised.

Strong unique passwords and 2FA as complementary defences

Lockout policies and rate limiting slow an attack down, but they work best alongside good habits at the account level. A long, unique password for every site removes the risk that a breach elsewhere hands an attacker a working credential stuffing pair, and a password manager makes this practical without having to memorise dozens of strings. Two-factor authentication adds a further layer on top: even if an attacker does correctly guess or obtain a password, whether through brute forcing or credential stuffing, they still need the second factor to actually log in. None of these measures is a complete solution on its own, but together they address the problem at every stage: reducing the odds of a correct guess, slowing down the attempt itself, and providing a backstop if a password does get through.

Summary

Brute force attacks guess passwords systematically, while credential stuffing reuses real credentials leaked in previous breaches, and both rely on being able to make many attempts quickly. Account lockout policies and rate limiting directly undermine that assumption by capping how many attempts are possible, while strong, unique passwords and two-factor authentication reduce the odds of success and provide a backstop even when an attacker does get a password right. It is the combination that matters, not any single measure in isolation. Our security services are built around exactly that layered approach.

Get in touch

Drop our team a message today