Password advice has changed more than most people realize. Some of what was standard guidance a decade ago — force frequent changes, require a special character — is now considered outdated or even counterproductive by the organizations that actually study this, including NIST.
What actually makes a password strong
Length matters more than complexity. A long passphrase like "correct-horse-battery-staple" is dramatically harder to crack than a short, complex-looking password like "P@ss1!", because cracking difficulty scales with length far faster than with character variety. Current guidance generally favors longer minimum lengths over frequent forced rotation, which mostly just trains people to make small, predictable tweaks to the same password.
The single biggest real-world risk isn't a weak password — it's password reuse. If one of the dozens of services you use gets breached, and you reused that password anywhere else, attackers will try that same combination everywhere. This is called credential stuffing, and it's one of the most common ways accounts actually get compromised.
Password managers solve the reuse problem
A password manager generates and stores a unique, long password for every single account, so reuse simply stops being a temptation. The one password you actually need to remember is the master password protecting the vault itself — which is exactly why that one should be a genuinely strong, memorable passphrase.
MFA: not all methods are equal
Multi-factor authentication combines something you know (a password) with something you have (a device or key) or something you are (biometrics). Having some form of MFA is dramatically better than none — but the specific method matters more than most people realize.
MFA methods, weakest to strongest
- SMS/voice codes — better than nothing, but vulnerable to SIM-swapping and interception. Increasingly being phased out by major providers.
- Authenticator apps (Microsoft Authenticator, Google Authenticator, Authy) — meaningfully stronger, generates codes locally on your device rather than over the phone network.
- Push notifications — convenient, but vulnerable to "MFA fatigue" attacks where an attacker spams approval requests hoping for an accidental tap. Number-matching (confirming a specific code, not just tapping approve) closes this gap.
- Passkeys / hardware security keys — the strongest widely available option. Cryptographic, device-bound, and effectively phishing-resistant because there's no code to trick someone into typing into a fake site.
A quick setup checklist
- Use a password manager, and let it generate passwords rather than inventing your own
- Set a genuinely strong, unique master password on the password manager itself — this is the one you actually memorize
- Enable MFA everywhere it's offered, prioritizing authenticator apps or passkeys over SMS where you have the choice
- For any small business: enforce MFA at the organization level rather than leaving it optional per employee