Insights · Cybersecurity
What Did NIST Actually Change in Password Rules?
For years, nearly every security tip said the same thing: a complex password, one uppercase letter, a special symbol, and change it every 90 days. The authoritative US standard (NIST SP 800-63B) has effectively scrapped these rules — replacing them with something simpler and far more effective. Here's a direct breakdown of what changed, why, and what it means for you in practice.
Last updated: October 2026 · based on the fourth revision, NIST SP 800-63B-4 (final, August 2025)
The core idea: length, not complexity
The new guidance adopts a clear principle: a long, simple password is actually stronger than a short, complex one that's hard to remember. The practical result:
- Minimum length for a password used alone (as the single authentication factor): at least 15 characters.
- If the password is used within multi-factor authentication (alongside another factor like a code or biometric), 8 characters is the minimum.
- Systems must accept passwords of at least 64 characters, including spaces and Unicode characters.
What's banned outright
The most practically important point is what systems are now prohibited from forcing on users:
| Old rule | New status under NIST |
|---|---|
| Forcing a mix of upper/lowercase, symbols, and digits | Prohibited — full freedom is left to the user |
| Periodic password changes (every 60/90 days) | Prohibited without cause — only required when there's evidence of an actual compromise |
| Security questions and hints ("your first pet's name") | Fully prohibited as a way to create or recover a password |
| Letting a user see a hint for their password before logging in | Prohibited |
Instead, systems must screen every new password against lists of known, compromised values (breach corpora, dictionary words, repeated characters, the service's own name) and reject it if found — telling the user why and helping them pick a stronger alternative.
The real change: phishing resistance
This is the deepest shift. The new guidelines classify authentication methods by "Authenticator Assurance Level" (AAL1 through AAL3) and state clearly: passwords alone are never phishing-resistant — regardless of length or complexity. The same applies to codes sent by email or SMS.
- AAL2 (typical for most important accounts): systems must offer at least one phishing-resistant option (such as passkeys or a physical security key), and its use should be encouraged.
- AAL3 (highest sensitivity): phishing resistance is mandatory, and the private key must never be exportable.
The new guidelines also formally recognize "syncable authenticators" — simply, modern passkeys that sync across your devices through your Apple, Google, or Microsoft account.
A quick checklist for your personal accounts
- Turn on a passkey or two-factor authentication for any account that supports it (email, banking, social media)
- Use a password manager instead of memorizing or reusing passwords
- Make sensitive passwords 15+ characters — a long phrase is easier to remember than a short, complex code
- Don't change your passwords "just in case" on a schedule — only when you suspect an actual compromise
- Never reuse the same password across two important accounts
