Password Cracking Methods
Password cracking tests how well an organization's authentication defenses hold up against real-world attack techniques.
Brute Force Attacks
A brute force attack systematically tries every possible character combination until the correct password is found. It's slow but effective against short or simple passwords with no lockout policy in place.
Dictionary Attacks
Dictionary attacks use a pre-built list of common passwords and variations, exploiting the fact that many users still choose predictable, easily guessable passwords.
Hash Cracking and Rainbow Tables
Since passwords are typically stored as hashes rather than plain text, testers often work with captured hash values, using precomputed rainbow tables or GPU-accelerated cracking tools to reverse them.
Why Organizations Test This
Password cracking assessments reveal weak password policies before an attacker can exploit them, pushing organizations toward stronger authentication practices like multi-factor authentication.
Why Slow Hashing Changes Everything
The defence that matters most is how a password is stored. A fast general-purpose hash lets an attacker test enormous numbers of guesses cheaply. Purpose-built password hashing functions deliberately slow this down and tie it to memory use, so each guess costs far more effort. This single choice turns a trivial offline attack into an impractical one, which is why storage design matters more than the exact guessing method.
| Storage approach | Effect on an attacker |
|---|---|
| Plain text | No work needed — a breach exposes every password instantly. |
| Fast general hash | Billions of guesses per second are feasible. |
| Slow, memory-hard password hash | Each guess is deliberately expensive, so large-scale guessing becomes impractical. |
How Salting Defeats Precomputation
A salt is a unique random value stored alongside each password hash. Because every user's salt differs, identical passwords produce different stored hashes, and an attacker cannot reuse one precomputed table across many accounts. Salting is what makes precomputed lookup tables ineffective — they would have to be rebuilt for every single salt. A related value, sometimes called a pepper, can be kept separately from the database for an extra layer. Neither is secret in the way a password is; their job is to force per-account work.
Defences Every Team Should Apply
From a defender's point of view, the practical controls are well understood:
- Slow, salted password hashing for stored credentials — never plain text or a bare fast hash.
- Rate limiting and account lockout on login so online guessing is throttled.
- Multi-factor authentication, which keeps a stolen password from being enough on its own.
- Length over complexity — encourage long passphrases and screen new passwords against lists of already-breached ones.
- Monitoring for spikes in failed logins, a sign that guessing is under way.
A common mistake is trusting complexity rules alone; a short but "complex" password is often weaker than a long simple phrase. Security assessments test these controls precisely so gaps are fixed before a real attacker finds them.
Takeaway: credential security is won in storage and policy. Salted slow hashing, lockouts and multi-factor authentication together make guessing attacks far more costly than they are worth.