Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Brute Force Attack?

A brute force attack tries passwords, PINs, or keys one after another until one works. Learn how online and offline guessing differ and which controls stop them.

Illustration for the cybersecurity term Brute Force Attack
Home / Blog / Cybersecurity Terms / What Is a Brute Force Attack?
17 November 2026

What Is a Brute Force Attack?

What Is a Brute Force Attack?

A brute force attack is an attempt to discover a password, PIN, or cryptographic key by systematically trying candidates until one works. It needs no flaw in the software—only time, computing power, and a target that accepts or exposes enough guesses. That simplicity is exactly why it remains one of the most common routes to account compromise.

Online and Offline Guessing

The distinction that matters most to defenders is where the guessing happens.

In an online attack, every guess is sent to a live service: a Microsoft 365 sign-in page, an exposed Remote Desktop (RDP) port, an SSH daemon, a VPN portal, or an API login endpoint. The attacker is limited by network latency and by whatever throttling the service applies, and every failed attempt can leave a log entry. Tools such as Hydra and Medusa automate this against dozens of protocols.

In an offline attack, the attacker already holds password hashes—dumped from a breached database, extracted from a domain controller’s NTDS.dit file, or captured as a Wi-Fi handshake—and cracks them on their own hardware with Hashcat or John the Ripper. No lockout policy applies, nothing is logged on your side, and a single modern GPU can test billions of candidates per second against fast, unsalted hashes such as MD5 or NTLM. Here your only defence is how the passwords were stored and how long they are.

Variants Attackers Actually Use

MITRE ATT&CK tracks this family as T1110 Brute Force, with four sub-techniques that map neatly to real-world behaviour:

Pure exhaustive search—every combination of every character—is rarely worth it beyond short PINs. Dictionary and hybrid attacks deliver most of the results, because people choose predictable passwords.

Why Length Beats Complexity

Each extra character multiplies the search space. An eight-character password drawn from all 95 printable ASCII characters gives roughly 6.6 quadrillion combinations, which sounds a lot until you remember that cracking rigs work through fast hashes at billions per second. Add four more characters and the figure grows by a factor of more than 80 million. That is why the NCSC recommends passphrases built from three random words, and why NIST SP 800-63B favours length, screening against known-breached passwords, and no forced periodic changes over arbitrary composition rules.

Spotting an Attack in Progress

Online brute forcing is noisy if you are looking for it. Useful signals include:

Feeding these events into a SIEM with correlation rules turns them into alerts rather than log noise. Because attackers now distribute guesses across residential proxy networks, base your rules on the targeted account as well as the source address.

Controls That Work

  1. Multi-factor authentication. A correctly guessed password is far less useful when a second factor is required. Phishing-resistant options such as FIDO2 security keys or passkeys are best.
  2. Throttling and lockout. Cyber Essentials requires password-based accounts to be protected by MFA, by throttling to no more than 10 guesses in five minutes, or by locking out after no more than 10 unsuccessful attempts.
  3. Slow, salted hashing. Store passwords with Argon2id, scrypt, or bcrypt and a unique salt per user, as the OWASP Password Storage Cheat Sheet recommends, so stolen hashes are expensive to crack.
  4. Reduced exposure. Remove RDP and SSH from the internet, put admin interfaces behind a VPN or zero trust gateway, and disable legacy authentication.
  5. Breached-password blocking. Check new passwords against known-compromised lists and ban obvious choices such as the organisation’s own name.

Our two-factor authentication solutions help organisations roll out MFA across VPN, email, and remote access without disrupting users.

FAQ – Frequently Asked Questions

How Long Does a Brute Force Attack Take?

It depends on where the guessing happens and how the password is stored. Online guessing against a throttled service may manage only a handful of attempts per minute, so a long, unique password is effectively safe. Offline cracking of fast hashes such as NTLM can test billions of guesses per second, so short or common passwords fall in seconds. Long passphrases stored with Argon2id or bcrypt can take impractically long to crack.

Does Account Lockout Stop Brute Force Attacks?

Lockout slows guessing against a single account, but it does not stop password spraying, where attackers try one password across many accounts and stay below the threshold. It also does nothing against offline cracking. Aggressive lockout can even be abused to lock legitimate users out. Combine sensible lockout or throttling with MFA, breached-password screening, and monitoring for failed logons spread across many accounts.

Is It Legal to Brute Force My Own Systems?

Testing systems you own or are explicitly authorised to test is lawful, and password audits are a normal part of security assessments. Attempting to access anyone else’s systems without permission is an offence under the Computer Misuse Act 1990. Even internally, get written approval, agree the scope, and warn the service desk, because testing can trigger lockouts and alerts that look like a real attack.

Which Logs Should I Monitor for Brute Force Attempts?

Start with authentication logs: Windows Security events 4625, 4624, and 4740 on domain controllers, Entra ID or Okta sign-in logs, VPN and firewall authentication logs, and web application login records. Alert on many failures followed by a success, many accounts failing from the same source, and any sign-ins over legacy protocols. Centralising these in a SIEM makes cross-system patterns visible.

Related Terms

You May Be Interested In These

What Is Recovery in Incident Response?

Cybersecurity Terms

17 November 2026

What Is Recovery in Incident Response?

Read More
What Are JOSE, JWS and JWE?

Cybersecurity Terms

17 November 2026

What Are JOSE, JWS and JWE?

Read More
What Are Cyber Insurance Exclusions?

Cybersecurity Terms

17 November 2026

What Are Cyber Insurance Exclusions?

Read More