CPSA ยท Windows passwords, vulnerabilities and hardening
Online guessing vs offline cracking
Account brute forcing, rainbow tables vs hash brute force, salting and countermeasures.
Key points
- Online: a live service applies lockout, throttling, logging; spraying one password across accounts stays under per-account limits.
- Offline: guesses on the attacker's hardware, no lockout; speed set by hash algorithm and hardware.
- Rainbow tables: precomputed, disk for time; fail against salted hashes.
- Unsalted NT hashes: open to tables and fast GPU brute force.
- Defences: long passphrases, salted slow hashes, protected hash stores.
Practice questions
What is the main thing that makes precomputed rainbow tables useless against a hash?
- A unique random salt mixed into each password before hashing
- Storing the hash in upper case letters
- Locking the account after five failed sign-ins
- Hiding the username field in the login form
Show answer
Answer: A. A unique random salt mixed into each password before hashing
A unique random salt per password means a table would have to be rebuilt for every salt value. Longer hash output or hiding usernames do not stop precomputation in the same way.
Which controls reduce the risk from offline cracking of stolen password hashes?
- Long, random passphrases
- Restricting and monitoring access to hash stores such as the SAM and AD database
- Salted, deliberately slow hashes in applications you build
- A stricter account lockout threshold
- Disabling the guest account only
Show answer
Answer: A. Long, random passphrases, B. Restricting and monitoring access to hash stores such as the SAM and AD database, C. Salted, deliberately slow hashes in applications you build
Long random passphrases raise the work factor, and restricting who can read the hash stores prevents the theft. A lockout threshold only applies to live logons, so it does nothing here.
True or false: a big enough rainbow table can still crack password hashes that use a unique random salt per account.
Show answer
Answer: False
False. A table is built for one fixed hash function and no salt; with a unique salt per password the attacker would need a separate table for every salt, so they fall back to per-hash brute force.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
