Password Security•7 min read•

Should You Change Passwords Regularly? What NIST Says

Why NIST no longer recommends forced periodic password changes, the side effects of the 90-day rule and when a password really should change.

What do you do when your password expires every 90 days? Most people turn November2026! into December2026! and get on with their day. For years periodic password changes were considered good practice, yet they often do the opposite: they push people towards more predictable passwords. This guide covers where the habit came from, why NIST dropped it and what actually improves password security.

Where Periodic Password Changes Came From

Forced rotation dates from the era of shared computers. The reasoning: even if an attacker obtains a password, it will change soon and the stolen information will expire.

It rested on two assumptions:

  • Passwords are cracked slowly, by hand.
  • Users pick a completely new, strong password every time.

Neither holds today. Stolen credentials are tried quickly with automated tools, so attackers do not wait for a password to expire. And users mostly tweak the old password instead of creating a new one.

Why NIST No Longer Recommends Regular Changes

In 2017 the US National Institute of Standards and Technology (NIST) published SP 800-63B and stated clearly that memorised passwords should not be forced to change without reason. Revision 4, published in 2025, made it even firmer: systems should not require users to change passwords periodically.

NIST's core principles:

  • Length comes first. Under Rev. 4, a password used on its own should be at least 15 characters, and at least 8 when it is part of multi-factor authentication; lengths up to at least 64 characters should be supported.
  • No arbitrary complexity rules. "One capital, one symbol" rules push users into patterns.
  • Changes need a reason. Without evidence of compromise, a forced change should not be imposed.
  • Check breach lists. Passwords known from earlier breaches should be blocked at sign-up and change.
  • Allow pasting. Password manager users should be able to paste.
  • No hints or security questions. "Your first pet's name" is not a security layer.

NIST is not alone: the UK National Cyber Security Centre (NCSC) also advises against forced periodic changes, and in 2019 Microsoft removed password expiration from its Windows security baseline recommendations. The setting still exists and can be managed through Group Policy.

The Side Effect: Predictable Patterns

The real problem appears in behaviour. To remember passwords, people make small, regular changes:

  • Season and year: Summer2025! → Autumn2025!
  • Increment the number: Cat34 → Cat35
  • Add or change a character: London! → London!!

To the user it looks like a new password; to an attacker who knows the old one, the new one is far easier to guess. A 2010 study at the University of North Carolina found that an attacker who knew a user's old password could find the new one with very few guesses for a large share of accounts.

The irony: a rule designed to stop attackers produces a chain of predictable passwords that helps them.

The Psychology: How Users Transform Passwords

The more people must remember, the more they look for shortcuts. Every forced change asks one question: "How do I get through this with the least effort?"

The answer is usually one of three behaviours:

  1. Transformation: a small variant of the old password.
  2. Cycling: rotating between a few passwords used before.
  3. Writing and sharing: noting the password down or using the same one everywhere.

Each forced change also produces forgotten passwords, lockouts and help desk tickets. Users tire of security rules, a state known as "security fatigue", and start ignoring all of them.

When Should a Password Really Change?

There is a healthy middle ground between "never" and "constantly": event-driven changes. Change your password immediately when:

  • It appears in a breach list.
  • Another service where you used the same password is breached. Attackers try leaked lists on other sites automatically (credential stuffing).
  • You see a session or activity you do not recognise.
  • You fell for phishing and typed your password into a fake page.
  • You suspect malware on your device.
  • You shared the password with someone who should no longer have it.

Note: human and machine accounts differ. Service accounts and API keys do not depend on human memory, so automatic rotation through a vault remains good practice.

What to Focus On Instead

Layer What it gives you
Long, unique password Resistance to brute force
Password manager A different strong password for every account
Two-step verification (2FA) Blocks sign-in even if the password leaks
Breach monitoring Early warning of compromise
Phishing awareness Stops the password being stolen in the first place

In practice: choose a random password of 15 characters or more for each account, unique to that account; keep them all in a password manager; add two-step verification to critical accounts. Where possible move to phishing-resistant methods such as passkeys and FIDO2.

Moving an Organisation to Modern Standards

The "90-day rule" usually comes from an old policy document nobody questions. Moving to the NIST approach takes four steps (details in the corporate password policy guide):

  1. Update the policy. Remove forced periodic changes and adopt event-driven changes.
  2. Adjust technical controls. Raise the minimum length (NIST Rev. 4: 15 characters for a password used on its own), allow up to 64 characters, do not block pasting.
  3. Turn on breach screening. Block known breached passwords at sign-up and change.
  4. Roll out two-step verification. This is what actually takes over the protection rotation was supposed to provide.
Old policy NIST SP 800-63B approach
Forced change every 60–90 days Change only with a reason
Mandatory complexity rules Length first, no arbitrary rules
Short maximum length Support up to at least 64 characters
Paste blocked Paste allowed
Hint questions No hints or knowledge-based questions
No breach check Screening against breach lists

Communication matters too. "You no longer need to change your password" on its own is easily misread. The right message: "You will change your password when it is needed, not for no reason, and we are giving you stronger tools for that."

Summary

Periodic password changes were well meant but ignored human nature. They pushed users towards predictable passwords, written-down passwords and security fatigue rather than stronger ones.

The modern approach in one sentence: a password change is triggered by an event, not by a calendar. With evidence or strong suspicion it changes; otherwise its strength comes from length and uniqueness.

Frequently Asked Questions

Should I never change my password? Not "never", but "not needlessly". If your password is strong, unique and protected by two-step verification, changing it for no reason adds nothing. Change it at once after a breach, a suspicion or sharing.

My company still requires a change every 90 days. What should I do? You have to follow the rule. The safest approach is to generate a completely new random password with a password manager each time. If you are a decision maker, bring the NIST SP 800-63B approach into the policy discussion.

What is NIST, and is it binding on me? A US standards body. Its guidelines are not legally binding, but they are the de facto reference for corporate security policies worldwide.

How do I know whether my password has leaked? The breach checker uses k-anonymity: your password is not sent; only the first 5 characters of its SHA-1 hash are queried.

How many characters are enough? NIST SP 800-63B Rev. 4 requires at least 15 characters for passwords used on their own and at least 8 for those used with multi-factor authentication. 15 characters or more is a good practical target.

Need a Change for a Real Reason? Generate It Safely

Use the Password Generator: the password is created in your browser with cryptographically secure randomness (crypto.getRandomValues) and is never sent or stored. It can also clear the clipboard automatically 60 seconds after copying.

The Password Strength Test estimates how long your current password would take to crack on a GPU, and the breach checker shows whether it appears in known breach lists. Prefer something memorable? Try the Passphrase Generator.

Generate Strong Credentials Instantly

Hardware-backed Web Crypto API with zero logging and zero server contact.

Open Password Generator →