Brute-Force Attack
Pronunciation: BROOT FAWRS uh-TAK
Definition
Brute-Force Attack is an attack or weakness pattern that repeatedly tries passwords, keys, codes, or other possibilities until one succeeds or a usable weakness appears. For Brute-Force Attack, an attempted action, a detected indicator, a confirmed compromise, and a realized loss are separate states that require different evidence and response.
Overview
Meaning and scope
Brute-Force Attack is an attack or weakness pattern that repeatedly tries passwords, keys, codes, or other possibilities until one succeeds or a usable weakness appears. For Brute-Force Attack, an attempted action, a detected indicator, a confirmed compromise, and a realized loss are separate states that require different evidence and response.
Mechanism and operation
A brute-force attack uses repeated guesses to discover a valid password, one-time code, cryptographic key, recovery answer, or hidden value. Attempts may be exhaustive, dictionary-based, distributed across sources, or optimized using leaked information and common patterns. Offline attacks operate on stolen password hashes or encrypted data, making strong algorithms, salts, key derivation, and credential complexity especially important. Defenses include multifactor authentication, breached-password blocking, progressive delays, device and network correlation, secure hashing, monitoring, and alerts. Lockout rules require care because attackers may deliberately trigger them to deny access to legitimate users. Brute-force resistance combines strong credentials and cryptography with rate controls, multifactor authentication, monitoring, and denial-of-service-aware lockout design.
Practical payment example
An attacker automates guesses against a weak password or secret. Rate limits and stronger authentication reduce exposure but do not excuse stored-secret leakage.
Operational checks
Assessment of Brute-Force Attack should trace an attack or weakness pattern that repeatedly tries passwords, keys, codes, or other possibilities until one succeeds or a usable weakness appears from prerequisite and entry point through observable impact on the affected service. Prevention, detection, containment, and recovery for the Brute-Force attack path should be tested against the architecture associated with attack, weakness pattern that repeatedly tries passwords, and keys.
Distinctions and limits
Online attacks interact with the target and can be slowed through rate limits, lockouts, challenges, and risk detection. A theoretical weakness or scanner result involving attack, weakness pattern that repeatedly tries passwords, and keys should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Related reading
Related definitions: credential, authentication.
Example
An attacker automates guesses against a weak password or secret. Rate limits and stronger authentication reduce exposure but do not excuse stored-secret leakage.
Comparison
Online attacks interact with the target and can be slowed through rate limits, lockouts, challenges, and risk detection. A theoretical weakness or scanner result involving attack, weakness pattern that repeatedly tries passwords, and keys should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Key Takeaway
Brute-force resistance combines strong credentials and cryptography with rate controls, multifactor authentication, monitoring, and denial-of-service-aware lockout design.
Sources
- NIST Documentation: Cryptographic Standards And Guidelines — NIST (2026-07-30)