proTECHtusDailyThe publication arm of Protechtus · for every‑day users
Free Guides  /  Security  /  Guide № 03
SecurityChecklistPrintable
Checklist · tick as you go

Passwords, for normal humans.
One idea, a few settings, twenty minutes.

Why reusing a password is the real danger, and the short list of settings that actually protect you.

Security · guide № 03
Passwords, for normal humans.
One idea, a few settings, twenty minutes.
  1. §01The one idea
  2. §02What current guidance actually says
  3. §03A password manager
  4. §04Passkeys in plain words
  5. §05The second factor
  6. §06Recovery codes and the lockout trap
  7. §07The 20-minute list
verified 2026-11-09 · protechtus.com
Length
7 min
1467 words
Status
Verified
checked 2026-11-09
Format
Web + print
Priority order. The top of each list matters most.
Sources
17
primary sources, resolved
Price
Free
read, print, share

§01 · The one idea

Most account takeovers do not start with someone guessing a clever password. They start with a password that already leaked from another site, tried on yours. Credential stuffing means taking username and password pairs from one breach and trying them on other services. In a large 2025 breach study, compromised credentials were how attackers got in for 22 percent of the breaches reviewed [7].

Reuse makes it easy. On devices infected with password-stealing software, the typical person had just 49 percent of their saved passwords be distinct [7]. Half were copies. If someone gets one reused password, they can use it on your other accounts [8].

So the goal changes. A long, clever password used in two places is exposed the moment either place leaks it. Uniqueness beats cleverness, and software has to remember the passwords for you.

◆ Start here

Give every account its own password, and let a password manager remember them. That one habit addresses the main risk in this guide [6][7].

§02 · What current guidance actually says

The main US technical standard for sign-in systems sets these requirements [1].

  • Length counts: at least 15 characters when a password is your sole sign-in step [1].
  • Sites must not force rules like "one capital, one number, one symbol" [1]. Those rules push people toward workarounds, and very complex passwords get written down unsafely [2].
  • NIST prohibits periodic forced password changes. A change is required when there is evidence of compromise [1].
  • Security questions ("your pet's name") are not allowed at password creation [1].

Change a password when you get a breach notice or a manager alert [1]. If your employer forces rotation, comply, but do not copy the habit. These rules bind organizations that run login systems, not individuals [1].

§03 · A password manager

A password manager keeps your logins in an encrypted vault, fills them in, and generates random passwords. You remember one secret.

  • Pick one. Built-in managers from Apple and Google are named in CISA guidance alongside standalone products such as 1Password, Dashlane, Keeper, Proton Pass and LastPass [6]. The sources do not rank them.
  • One ecosystem? Use the built-in one. Mixed devices? Check the manager works in your browsers and on your phone before you commit.
  • Make the master password long, unique and random. CISA advises a strong passphrase for the vault, and replacing weak old passwords with generated ones [6].
  • Write the master passphrase down and keep it somewhere safe at home. Also set up whatever recovery the manager offers, such as an emergency kit or recovery key.
  • Turn on two-step verification for the manager account itself. Apple's iCloud Keychain, for one, requires it on the Apple Account [9].
  • Act on the alerts. Google's Password Checkup flags reused, exposed or weak passwords [8]. Fix email, banking and the manager account.

In 2022, attackers copied backups of LastPass customer vaults, which held some unencrypted details, such as website addresses, next to the encrypted fields. LastPass said the encrypted fields stayed protected by 256-bit AES and that it did not know customers' master passwords [14]. That is the company's own account, so treat it as a claim, not an audit. A long, unique master passphrase is what protects a stolen vault.

§04 · Passkeys in plain words

A passkey replaces your password with a matched pair of digital keys tied to one account on one site. The site keeps just the public key, so a database breach leaks no shared secret [3]. You approve a sign-in by unlocking your device with a fingerprint, face, PIN or pattern; the biometric data stays on the device [3].

The big win is phishing. A passkey is bound to the real website, so a lookalike page cannot collect a usable credential [3]. CISA calls FIDO/WebAuthn, the standard behind passkeys and security keys, the widely available method that resists phishing [4][5].

There are two kinds. Synced passkeys are stored by a provider and encrypted across your devices. They are easier to recover, but depend partly on protecting that provider account. Device-bound passkeys, including those on hardware security keys, stay on one device. That is the highest assurance, but losing the device can mean losing access without a backup [3].

When a site offers a passkey, accept it in the manager you use, but keep the password and a second factor in place until your recovery codes are on paper and a backup key is registered. Steps 4 to 7 in section 7 give the order.

Where passkeys work in 2026:

  • Apple devices, through iCloud Keychain [9].
  • Google accounts, through Google Password Manager [10].
  • Microsoft, through Edge and Microsoft Password Manager, with a Windows 11 plug-in for other browsers and apps. Availability varies [11].
  • Phone to laptop: your phone can approve a sign-in on another device, typically by QR code [3].
  • Adoption: an industry report from May 2026 counts 5 billion passkeys in use, though it comes from the group that promotes them. It also says 57 percent of organizations that rolled out passkeys still rely on phishable sign-in for everyday use [12].

§05 · The second factor

A second factor is the extra step after your password. Start with email, your password manager and your financial accounts. Email matters most: it resets everything else.

  • Before you change anything, save your recovery codes and register a backup key. Steps are in section 6 [16][17].
  • Top choice: a security key or passkey. CISA ranks FIDO/WebAuthn at the top [4][6].
  • Next: an authenticator app. Stronger than text messages, but it can still be phished, for example by a fake login page that relays your code [4][6].
  • Last resort: text or voice codes. CISA says to use them as a last resort, because they are open to phishing, SS7 exploitation and SIM swap [4]. Text messages are also not encrypted [6], and Google notes that codes sent by text or call can be exposed to phone-number-based hacks [16].
  • If text is all a site offers, still turn it on. CISA says "any MFA is better than no MFA" and people who turn on MFA are significantly less likely to be hacked [5]. Microsoft claimed in 2019 that MFA blocks over 99.9 percent of account compromise attacks, a vendor statement, not independent measurement [13].
  • If you are a likely target, go to keys. Google's Advanced Protection Program requires a passkey or security key to sign in [15]. Its recovery can take days, so register a backup key before enrolling (section 6) [17].
  • Last, remove text codes where you have something better. Adding an authenticator app does not automatically remove SMS, which can leave a weak fallback [6]. Do not turn off text codes until the app or key works and the recovery codes are on paper.

§06 · Recovery codes and the lockout trap

◆ The trap

People harden the front door and leave a weak back door. Some services default to a text message during account recovery, so removing SMS from login may not remove it from recovery [6].

Audit recovery on your email, manager, Apple, Google or Microsoft account, and bank.

  • Generate backup codes for key accounts. Google's are 8 digits, can be printed or downloaded, and should not be shared [16].
  • Store them offline, printed and somewhere safe, or in your manager's secure notes. Not in the inbox they protect.
  • Register a backup security key if you use keys. Google recommends a primary key and at least one backup [17].
  • Learn your platform's recovery path before you need it. Apple's passkey recovery needs your iCloud credentials, an SMS response and your device passcode, with an optional recovery contact [9].
  • Know the price of strict protection. Under Google's Advanced Protection, recovery takes a few days while identity is verified [17]. That friction is deliberate.
  • Keep your recovery email and phone current. An old address you no longer control is a way in.

§07 · The 20-minute list

In order of value:

  1. 01.

    Pick a password manager.

    Built-in is fine if it covers your devices [6].

  2. 02.

    Set a long random master passphrase,

    write it down and keep it somewhere safe at home, turn on two-step verification for the manager account [6][9] and save its recovery code when it is shown, and set up whatever recovery the manager offers.

  3. 03.

    Run the breach and reuse check,

    such as Google's Password Checkup, and replace reused passwords, starting with email, banking and the manager [8].

  4. 04.

    Save recovery codes on paper

    and register a backup security key if you use keys. Check what recovery requires on each account [16][17].

  5. 05.

    Add an authenticator app or key,

    and keep your password and text codes in place until it works [6].

  6. 06.

    Add a passkey

    wherever one is offered on an important account, still keeping the password as a fallback [3].

  7. 07.

    Then remove text codes

    where you have something better, never before steps 4 and 5 are done [6].

  8. 08.

    Skip

    forced rotation and symbol rules [1][2].

Sources

Every claim above points at one of these. They were checked on 2026-11-09. If one stops being true, this page will say so.

  1. 1.NIST SP 800-63B-4, Authenticator and Verifier Requirements · Length, rotation, SMS, recovery ruleshttps://pages.nist.gov/800-63-4/sp800-63b/authenticators/
  2. 2.NIST SP 800-63B-4, Passwords appendix · Why complexity rules often backfirehttps://pages.nist.gov/800-63-4/sp800-63b/passwords/
  3. 3.FIDO Alliance, Passkeys · How passkeys work, two kindshttps://fidoalliance.org/passkeys/
  4. 4.CISA, Implementing Phishing-Resistant MFA fact sheet · Phishing resistance and SMS weaknesseshttps://www.cisa.gov/sites/default/files/publications/fact-sheet-implementing-phishing-resistant-mfa-508c.pdf
  5. 5.CISA, More than a Password · Any MFA beats no MFAhttps://www.cisa.gov/MFA
  6. 6.CISA, Mobile Communications Best Practice Guidance · Manager advice, SMS, recovery defaultshttps://www.cisa.gov/sites/default/files/2025-12/guidance-mobile-communications-best-practices_508c.pdf
  7. 7.Verizon, Credential stuffing attacks: additional 2025 DBIR research · Credential stuffing and reuse figureshttps://www.verizon.com/business/resources/articles/credential-stuffing-attacks-2025-dbir-research/
  8. 8.Google, To stay secure online, Password Checkup has your back · Password Checkup and exposed passwordshttps://blog.google/technology/safety-security/password-checkup/
  9. 9.Apple Support, About the security of passkeys · Apple passkey sync and recoveryhttps://support.apple.com/en-us/102195
  10. 10.Google Account Help, Sign in with a passkey instead of a password · Google passkeys via Password Managerhttps://support.google.com/accounts/answer/6197437
  11. 11.Microsoft, Passkeys in Microsoft Edge · Microsoft Edge passkeys and PINhttps://explore.microsoft.com/en-us/edge/features/passkeys
  12. 12.FIDO Alliance, The State of Passkeys: Global Consumer and Workforce Report (2026-05) · Passkey adoption figures, May 2026https://fidoalliance.org/wp-content/uploads/2026/05/The-State-of-Passkeys-Global-Consumer-and-Workforce-Report-1.pdf
  13. 13.Microsoft Security Blog, One simple action you can take to prevent 99.9 percent of account attacks · Vendor claim about MFA effectivenesshttps://www.microsoft.com/en-us/security/blog/2019/08/20/one-simple-action-you-can-take-to-prevent-99-9-percent-of-account-attacks/
  14. 14.LastPass, Notice of Recent Security Incident · LastPass 2022 incident vendor accounthttps://blog.lastpass.com/posts/notice-of-recent-security-incident
  15. 15.Google, Advanced Protection Program · Advanced Protection requires a keyhttps://landing.google.com/advancedprotection/
  16. 16.Google Account Help, Turn on 2-Step Verification · Backup codes and text-code riskshttps://support.google.com/accounts/answer/185839
  17. 17.Google Account Help, Advanced Protection account recovery and security keys · Backup keys and slow recoveryhttps://support.google.com/accounts/answer/7539956
What we could not confirm
  • Which password manager is better. We found no independent, primary-source head-to-head testing, so no product is recommended over another.
  • Whether passkeys can move freely between providers, and whether Windows-stored passkeys sync to phones in every setup. Sources conflict. Check the current vendor instructions before moving passkeys, and keep a second way in.
  • Manager-specific recovery options, such as emergency kits or recovery keys. We could not confirm what each product offers, so check your manager's own help pages.
  • The Microsoft 99.9 percent figure, Google's exposed-password counts and the passkey adoption numbers are claims by vendors or an industry group about their own products.
  • The standard NIST publishes binds the organizations that run sign-in systems, not individual users. Some parts of it, including the sections on syncable authenticators and account recovery, were not read in full.
  • The CISA fact sheet on phishing-resistant MFA is dated 2022. Its principles are repeated in later guidance, but ranking details could change.
✉ The Dispatch

An email when there is something worth sending.
Honest, brief, forwardable.

Scam shapes, one explainer, and one thing worth printing out, when there is an issue worth sending. Sign-ups are open; the first issue goes out when there is one.

Free · no fixed schedule · unsubscribe anytime