A password is a key, and 7.2 already told you what makes a key strong. Today: why length beats cleverness, why reusing a password is the real disaster, and the five minutes that protect an account better than anything else.
No reading — this page is the reading. Bring 7.2’s idea: strength comes from the number of possible keys.
Security, at the front door. Encryption protects data on the way. Authentication decides who gets in.
Authentication is proving you are who you say you are. There are three kinds of proof, called factors:
| Factor | Examples | Beaten by |
|---|---|---|
| something you know | password, PIN, security answer | guessing, a breach, phishing |
| something you have | your phone (a code or an app prompt), a security key | physically stealing it |
| something you are | fingerprint, face — biometrics | very hard to fake remotely |
Password strength is key space. Each extra character multiplies the number of possible passwords, so length beats complexity: four random words beat eight characters of symbols.
Reuse is the actual catastrophe. When one site is breached, attackers try the same email and password on hundreds of other sites automatically. One leak unlocks every account that shares the password. A password manager — an app that generates and remembers a different strong password for every site — is the practical fix.
Part 1. How long would it take a fast attacker to try every possible password? (We assume 10 billion guesses per second — a fast offline attack on a stolen database. Real speeds vary a lot, but the comparisons hold.)
Part 2. Multifactor, or not?
Five questions. “Which of these is multifactor?” is a regular.
Pick the account you’d least like to lose — usually your main email, because it can reset every other password. Turn on multifactor in its security settings. It’s the highest-value five minutes of this unit. (Don’t type real passwords into any class activity, including this page — the tool above asks for a length, not a password.)