Password and Account Security Checklist
What current guidance actually says: length over symbols, a manager, two-factor on email first, no forced rotation, and how to get back in if you lose your phone.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Password and Account Security Checklist?
Most password advice is decades out of date. Forced ninety-day changes, a symbol and a digit, and a complexity meter that rewards substituting zero for the letter O: none of that survives contact with the current guidance from the bodies that set it. The modern answer is shorter and easier, which is why it is worth reading.
The list is ordered by how much risk each step removes. The first four items do most of the work. The rest closes the gaps: what is already exposed, and whether you could get back in after losing your phone, which is the failure most people have never thought about until it happens.
- Ordered by how much risk each step removes, not by category
- Reflects current standards guidance: length and uniqueness over rotation and symbols
- Links the Password Strength Checker for testing a passphrase without sending it anywhere
- A recovery section for the lost-phone case most advice omits
- Editable and exportable as PDF, CSV, Markdown or a Google Form
Updated
How to use the Password and Account Security Checklist
- Start with a password manager, then change email and banking passwords to generated ones.
- Turn on two-factor authentication on email first, then banking, cloud storage and social accounts.
- Check your addresses against known breaches and change those passwords before anything else.
- Register a second two-factor method and save recovery codes somewhere offline.
- Review connected apps and signed-in devices, and close accounts you no longer use.
Worked examples
Starting from reused passwords
Input
Essentials only
Output
Manager, unique passwords, two-factor on email
Three steps remove most of the realistic risk.
Address appeared in a breach
Input
Exposure section
Output
Those passwords changed first, old accounts closed
Leaked pairs are being tried against other sites right now.
Worried about losing your phone
Input
Recovery section
Output
Second method registered, codes stored offline
Turns a lockout into an inconvenience.
Background and insight
The shift in official guidance came from watching what rules do to behaviour. Forced rotation pushes people toward predictable patterns, usually the same password with an incrementing number, which is weaker than leaving a strong one alone. Complexity rules push them toward short strings full of substitutions that attackers' tools already expand. Both standards bodies now favour length, uniqueness and screening against known-breached passwords, and advise changing a password when there is evidence of compromise rather than on a timer.
Reuse is the actual attack. When a service is breached, the leaked email and password pairs are tried automatically across every other popular service, at scale. This is credential stuffing, and it is why a single unique password per site matters more than how clever any one of them is. A manager is the only practical way to do that for a hundred accounts.
Email deserves its own protection because it is the recovery route for everything else. Whoever controls your email can reset your bank, your cloud storage and your social accounts in sequence. That is why two-factor goes on email before anything else, and why an app or hardware key beats SMS: SIM swapping, where an attacker has your number moved to their device, is common enough to matter.
Recovery is the part people skip. Two-factor without a second method turns a lost phone into a permanent lockout. Recovery codes stored only on the device they protect are no help. Both are cheap to fix in advance and impossible to fix afterwards.
Common use cases
A yearly security pass
An hour that removes most of the risk of an account takeover.
After a breach notification
What to change first, and how to find what else is exposed.
Helping family
Plain steps for someone who has used the same password everywhere.
Small teams
A baseline to adopt before writing a longer policy nobody reads.
Tips and limitations
- Three or four random words beats a short string of substitutions, and is far easier to type.
- Treat security questions as extra passwords. Your mother's maiden name is public; store a random answer.
- Use passkeys where offered: there is no secret to type into a fake page, so they cannot be phished.
- Revoke connected apps you no longer use. Old integrations keep their access indefinitely.
- Close dormant accounts. They hold personal data and are breached at the same rate as active ones.
Sources and further reading
- Digital Identity Guidelines (SP 800-63B), National Institute of Standards and Technology. The standard that dropped forced rotation and complexity rules
- Password policy: updating your approach, National Cyber Security Centre. Why rotation and complexity backfire
- Multi-Factor Authentication, Cybersecurity and Infrastructure Security Agency. Comparison of second-factor methods
Frequently asked questions
Does this checklist still tell me to rotate passwords?
No, and deliberately not. Current guidance from both NIST and the NCSC advises against forced rotation, because it drives people toward predictable patterns such as the same password with an incrementing number. Change a password when there is reason to think it is compromised.
What makes a strong password now?
Length and uniqueness. Three or four random words is stronger than a short string full of symbol substitutions, and much easier to type. Uniqueness matters more than either, which is why a manager generating a different password per site is the real answer.
Which account should I protect first?
Email. Whoever controls it can reset your bank, your cloud storage and your social accounts in sequence, so it is the account that protects all the others. Turn two-factor on there before anywhere else.
Is SMS two-factor good enough?
It is better than nothing and worse than the alternatives. SIM swapping, where an attacker has your number transferred to their device, is a real and common attack. An authenticator app or a hardware key removes that route entirely.
What happens if I lose the phone with my authenticator?
Without preparation, potentially a permanent lockout. Register a second method, such as another device or a hardware key, and store recovery codes offline or in your password manager on a different device. Both are easy beforehand and impossible afterwards.
Is there an in-depth guide to the Password and Account Security Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.