password hygiene & account security
password managers, 2fa, passkeys, hardware mfa — what to actually use and why
core rules
- never reuse passwords across sites — one breach cascades to every account that shares the password
- never save passwords in your browser’s built-in manager — browser vaults are trivially decrypted by any malware with local access
- never use personal info (name, dob, family, pet, sports team) — anyone with a cursory web search can derive these
- rotate passwords for critical accounts (email, bank, cloud, identity) every 3–6 months; more often if you suspect exposure
- use a real password manager for everything
- use 2fa everywhere it’s offered
- never share passwords — even with people you trust. use a manager’s share feature if you must
password hygiene isn’t about picking one clever password — it’s about how the system fails. a strong password is worth nothing if it’s shared with the site that leaked last year, and a weak password on a low-value account still matters if it opens the door to the email that resets everything else.
what a good password looks like
- uppercase, lowercase, numbers, and top-row symbols
- use spaces if the site allows them — they widen the keyspace attackers must brute-force
- 16+ characters. length beats complexity at high lengths
- generated by your password manager, not by you
- never use emojis — unicode codepoint differences between platforms mean the password may not match on another device
the old “P@ssw0rd!” advice is dead. modern password crackers know every substitution pattern humans reach for and try them in the first few million guesses. what actually resists brute force is length and randomness — a manager-generated 24-character random string is trivially better than any “creative” password you can memorize, and you never have to remember it anyway.
password managers
the specific manager matters less than actually using one. all of the reputable managers below use zero-knowledge encryption; the vendor cannot read your vault. the master password is the single most valuable secret in your life — make it long, unique, and write it down somewhere physical (safe deposit box, home safe).
| manager | type | notes |
|---|---|---|
| 1Password | cloud | polished ui, family sharing, secret key adds a second factor to your master password |
| Bitwarden | cloud / self-host | open source, generous free tier, self-hostable (vaultwarden) if you want your own server |
| LastPass | cloud | widely used but had major breaches in 2022 that exposed encrypted vaults; treat historical vault contents as compromised if you were a user then |
| Keeper | cloud | enterprise-friendly, strong compliance story |
| Dashlane | cloud | built-in vpn on higher tiers, dark-web monitoring bundled |
| KeePass | local | free, open source, offline-only; vault is a file you sync yourself. steepest learning curve; best if you don’t trust cloud vaults at all |
email hygiene
- don’t reuse your primary email across every site — the email is half your credentials, and it’s the reset vector for the other half
- use a mask/relay service (mozilla relay, apple hide-my-email, addy.io) to generate a unique forwarder per site
- use plus-addressing (
you+netflix@gmail.com) to identify who leaked your address when you start getting spam — but note some sites strip plus signs, so this is a supplement, not a replacement, for relays
email addresses are your login username almost everywhere. treat them the same way you treat passwords — not one address for the whole internet. relay services give you a unique forwarder per site; when one site leaks, only that one address becomes spam-bait and you can disable it in a click without touching your real inbox.
2fa / mfa
- hardware security key (yubikey, titan, nitrokey) — strongest, phishing-resistant
- passkeys — nearly as strong, easier to set up (see next section)
- totp app (aegis, ente auth, 2fas, google authenticator, authy) — strong; the 6-digit rotating code
- push-based mfa (duo, microsoft authenticator push) — ok, watch for prompt-fatigue attacks
- email codes — weak; only as strong as your email account
- sms codes — weakest; use only if nothing else is offered
the two main 2fa flavors are totp (time-based one-time password — the 6-digit code that rotates every 30 seconds in your authenticator app) and hotp (hmac-based one-time password — the same idea but incremented by a counter instead of the clock, used by some hardware tokens without an internal clock). both are strong; use whichever your account and device support.
passkeys
passkeys replace both the password and the second factor with a cryptographic keypair stored on your device. they can’t be phished, guessed, or brute-forced, and the private key never leaves your device. use them wherever a site offers them.
two flavors matter:
- synced passkeys — the private key is stored in a cloud vault (icloud keychain, google password manager, 1password, bitwarden) and syncs to your other devices. easier to recover if you lose a device; less secure because the key material is in the cloud (still encrypted under your account credentials)
- device-bound passkeys — the private key lives in the device’s secure enclave (tpm, secure element, hardware key) and can never leave. strongest security. downside: if the device dies, you cannot recover the passkey — you need backup codes or a second registered device
for accounts you access from multiple devices and can’t afford to lock yourself out of, synced passkeys are the pragmatic choice. for your most sensitive accounts — a security key for your email, root aws credentials, or crypto exchange — device-bound passkeys on a hardware key are the safest option.
hardware keys
always register at least two hardware keys per account, so a lost key doesn’t lock you out. store the backup somewhere physically separate.
- Yubico YubiKey — the industry standard; supports fido2 / webauthn, totp, hotp, piv, openpgp. usb-a, usb-c, nfc, lightning variants
- Google Titan — fido2 / webauthn only; cheaper than yubikey; usb-c + nfc
- Nitrokey — open source firmware and hardware; the paranoid’s pick
site red flags
#, ;, /, $, @, or !” — that’s a strong signal that they’re storing your password in plaintext (or a poorly-escaped database column) instead of a hash. use a unique manager-generated password for that account, enable every mfa option they offer, and mentally flag it as untrustworthy.
- character restrictions on passwords (unless they’re banning obvious garbage like control characters)
- a low maximum password length (under 32) — a properly hashed password has no length ceiling worth worrying about
- the site emails you your password after signup — means they have it in the clear
- “forgot password” sends your existing password rather than a reset link — same problem
- only sms 2fa offered, no totp or hardware option — account is only as safe as your phone carrier