Password policy that follows NIST SP 800-63B: length, screening, and no forced rotation

Modern guidance favors long passphrases, screening against breached passwords, no arbitrary complexity rules or scheduled rotation, and password managers plus MFA. How to translate SP 800-63B into identity provider settings.

Lesson 6 of 10 · 11 min read · practice only with authorization

Diagram

Old rules versus current guidance

Follow the path. One example at a time.

Step 1 of 4

Length

At least 15 characters for single-factor, 8 minimum with MFA, and allow at least 64.

Illustration: Length
# Length
# At least 15 characters for single-factor, 8 minimum with
# MFA, and allow at least 64.
What changes the outcome
Rules

Upper, lower, digit, symbol

Rotation

Every 90 days

Result

Spring2026! then Summer2026!

The example on the open step is one illustration, or the fix you can paste into an application you own.

What this page is made of

3 pieces. Each one says what fails, who is affected, what you would notice, and what you change.

  1. Complexity rules

    What fails
    Composition rules lead to predictable patterns.
    Who is affected
    Users and their accounts.
    What you would notice
    Passwords like Company1!.
    What you change
    Drop composition rules and require length.
  2. Forced rotation

    What fails
    Scheduled changes produce small, guessable edits.
    Who is affected
    Users.
    What you would notice
    Passwords that increment a number each quarter.
    What you change
    Rotate on evidence of compromise only.
  3. Password managers

    What fails
    Unique random passwords are only practical with a manager.
    Who is affected
    Staff juggling many accounts.
    What you would notice
    Reuse across work systems.
    What you change
    Provide an enterprise password manager.

What changed in revision 4

NIST SP 800-63B revision 4 (2024 to 2025) turns several recommendations into requirements: verifiers shall not impose composition rules or periodic changes, shall screen against compromised lists, and shall allow at least 64 characters.

Check yourself

Recognition and the fix. Nothing here is a procedure.

1 / 3

Under current NIST guidance, when should passwords be changed?

Go deeper

Specific techniques, exercises, and glossary cards for this topic.

  1. 01Slow password hashesA password database will be copied eventually. Includes the diagram and a defensive fix.

Exercises

  1. 01Password policy and hash cost explorerChange length, character sets, and hash algorithm, and watch the offline guessing time move. Then test which policy-compliant passwords fall first anyway.
  2. 02Password hashing and salting visualizerSee what a leaked user table reveals with no salt, one site-wide salt, and per-account salts, using real SHA-256 hashes computed in your browser.