Skip to content
Password Generator Lab

How often should you change your password?

Why security agencies no longer recommend changing passwords on a schedule, the situations where you should change one right away, and what to do instead.

· 5 min read

Key takeaways

  • NIST, the UK's NCSC and Microsoft no longer recommend changing passwords on a schedule; NIST SP 800-63B-4 forbids requiring it.
  • Change a password immediately if it was in a breach, reused elsewhere, shared, typed on an untrusted device, or if you see activity you don't recognize.
  • Forced changes produce predictable passwords: a UNC study guessed the new password from the old one in fewer than 5 tries for 17% of accounts.
  • PCI DSS v4.0 still requires 90-day changes where a password is the only factor, but not where multi-factor authentication is used.
  • Unique, random passwords in a password manager, plus two-factor authentication and leak monitoring, protect you better than routine changes.

Last reviewed

For years the standard advice was to change your password every 60 or 90 days. Many workplaces still enforce it. But the organizations that write password guidance — NIST in the United States, the NCSC in the UK, and Microsoft — have all moved away from it. The modern answer is simple: don't change a good password on a schedule; change it right away when there's a reason to.

The short answer

If a password is long, random, unique to one account and stored in a password manager, you don't need to change it routinely. Change it immediately if:

  • the service tells you it had a breach, or you receive a security alert about your account;
  • the password shows up in a known breach — you can check privately with our leaked-password check;
  • you used the same password on another site, especially one that has been breached;
  • you shared it with someone who no longer needs access — a former colleague, partner or contractor;
  • you typed it on a device you don't trust, or a device of yours had malware;
  • you see logins, messages or purchases you don't recognize;
  • it's short or something you made up yourself — replace it with a generated one.

Why scheduled changes backfire

Forced expiry is meant to lock out an attacker who has learned your password. In practice, people respond to constant changes predictably: Spring2026! becomes Summer2026!, Password7 becomes Password8.

Researchers at the University of North Carolina measured this directly. Zhang, Monrose and Reiter studied password histories from more than 7,700 university accounts that had to be changed every three months, and built tools that guess a new password from the old one. As summarized by the U.S. Federal Trade Commission's then chief technologist, they found that for 17% of accounts, knowing the previous password let them guess the next one in fewer than 5 attempts. With a stolen password file, they could crack the new password for 41% of accounts within 3 seconds per account. The authors concluded that their study "calls into question the merit of continuing the practice of password expiration."

The NCSC lists the other costs:

  • new passwords are often only minor variations of the old ones;
  • people forced to change passwords are more likely to write them down or forget them, which means lockouts and help-desk resets;
  • stolen passwords are generally used immediately, long before a 90-day timer runs out;
  • an attacker already inside an account will probably see the reset request too.

In the NCSC's words, "the more often users are forced to change passwords, the greater the overall vulnerability to attack."

What the guidance says

SourcePosition on routine changes
NIST SP 800-63B-4 (2025)Services SHALL NOT require periodic password changes — but SHALL force a change when there is evidence of compromise. (The 2017 version already said SHOULD NOT.)
NCSC (UK)"Don't enforce regular password expiry." Change passwords when a compromise is known or suspected instead.
Microsoft 365Passwords never expire by default, and Microsoft labels "never expire" as the recommended setting for cloud-only accounts.
PCI DSS v4.0Exception: where a password is the only authentication factor, change it at least every 90 days or analyze account security dynamically. Not required where multi-factor authentication is used.

When a schedule still applies

Some organizations still have to rotate passwords for compliance. The most common case is PCI DSS, the security standard for systems that handle payment cards: its requirement 8.3.9 applies when a password alone protects access. The PCI Security Standards Council has confirmed that the rule doesn't apply to systems where multi-factor authentication is used — so adding a second factor is usually the better way to comply. Check your own contracts, insurers and industry rules before switching rotation off.

Shared and service accounts are a different case. Change their passwords whenever someone who knew them leaves the team; NCSC calls an effective "movers and leavers" process one of the defenses that replaces forced expiry.

What to do instead of changing passwords on a timer

  • Use a unique password for every account. Reuse turns one breach into many. A random password generator and a password manager make this effortless.
  • Make each one long and random. 16–20 random characters, or a 6-word passphrase for the few you must remember.
  • Turn on two-factor authentication. A second factor protects you during the window between a leak and the moment you notice it.
  • Watch for leaks. Sign up for breach notifications from Have I Been Pwned, act on the alerts your password manager raises, and check any password you're unsure about with our leak check.
  • For organizations: screen new passwords against breached-password lists, monitor sign-ins for unusual activity, lock inactive accounts, and force resets when you have evidence of compromise — all of which the NIST and NCSC guidance recommend.

If you need to change a password now

Change it on the service's own website or app (not from a link in an email), replace it with a newly generated password rather than a variation of the old one, and update every other site where you used the same password. Then sign out of other sessions if the service offers it, and turn on two-factor authentication.

Generate a new password · NIST password guidelines explained

Sources

Keep reading