Password Policy Best Practices in 2026 (NIST 800-63B, Explained)

The rules that made passwords worse, the evidence that killed them, and a policy template based on NIST SP 800-63B you can adopt this week.

The rules that made passwords worse

For twenty years the standard corporate policy was: at least eight characters, one uppercase, one lowercase, one digit, one symbol, changed every 90 days, no reuse of the last ten. It was written in good faith, and it produced Summer2024!, Summer2024!! and a sticky note on the monitor. The man who wrote the original 2003 NIST guidance, Bill Burr, has publicly said he regrets it.

In 2017 NIST rewrote the guidance as SP 800-63B, and the 2024 revision (63B-4) went further. The changes are backed by research on hundreds of millions of leaked passwords: composition rules produce predictable substitutions, rotation produces incremented passwords, and both increase help-desk load without slowing attackers.

What a modern policy requires

  1. Minimum length 8 characters for any password, and 15 characters when the password is the only factor. Allow at least 64 characters so passphrases work.
  2. Screening against a blocklist of breached and common passwords at the time of creation. This is the single most effective control: it removes the passwords attackers try first. Our common password checker and breach checker show what such screening catches.
  3. Multi-factor authentication for anything beyond a trivial account, with phishing-resistant methods (hardware keys, passkeys) for privileged access.
  4. Rate limiting and lockout on the login endpoint: no more than a few attempts per minute per account, so online guessing cannot get far.
  5. Proper storage: bcrypt, scrypt or Argon2id with parameters tuned to a few hundred milliseconds. See bcrypt vs Argon2 vs scrypt.
  6. Allow paste and password managers. Blocking paste in password fields forces short, memorable, reused passwords.
  7. Show the password on request (an eye icon) so users can type long ones correctly.

What it stops requiring

  • Composition rules. “Must contain a symbol” is now “should not require”. Users may use any printable character, including spaces and Unicode.
  • Periodic rotation. Change passwords when there is evidence of compromise, not on a schedule.
  • Security questions. Answers are guessable or public. Use MFA and account recovery codes instead.
  • Password hints. Stored hints leaked with Adobe’s 2013 breach and made cracking trivial.
  • Truncation. Systems must not silently cut passwords to 16 characters; the whole password is hashed.

A policy you can adopt

The following fits on one page and complies with NIST 800-63B-4 for most organisations. Adjust the numbers where a regulator (PCI DSS 4.0 asks for 12 characters and alphanumeric) requires more.

Passwords must be at least 15 characters (8 where MFA is enforced) and may be up to 128 characters, containing any printable character. Passwords are checked at creation against a list of known-compromised passwords and rejected if found. Passwords do not expire; they are changed when compromise is suspected. Password managers are permitted and recommended. Passwords are never shared, written down in the open, or reused across systems.

Authentication requires a second factor for all remote access and all administrative accounts. SMS is not an acceptable second factor for administrative access. Login attempts are limited to 10 per hour per account.

Storage uses Argon2id or bcrypt with a work factor reviewed annually. Plain-text storage, reversible encryption, and unsalted or fast hashes are prohibited.

Testing candidates against a policy

The policy tester encodes the NIST, PCI, Entra and typical corporate rule sets and shows each check passing or failing for a candidate password. Use it to see what your current policy actually accepts, and to explain to stakeholders why Welcome1! passes the old rules and fails the new ones.

For onboarding, the bulk password generator produces compliant initial passwords in one click; set them to expire at first login.

Rolling it out

  1. Turn on breached-password screening first. It protects existing users immediately without a policy change.
  2. Raise the minimum length and remove composition rules at the same time, and tell users why: they are being asked for longer, simpler passwords, not more rules.
  3. Stop forced rotation. Expect the help desk to notice the drop in reset tickets within a month.
  4. Migrate storage to Argon2id or bcrypt by rehashing at next login.
  5. Roll out MFA, starting with administrators and email.

New tools and guides, about once a month.

No tracking pixels, no upsells. Unsubscribe with one click.

Newsletter