# NIST password guidelines explained (SP 800-63B-4)

Source: https://passwordgeneratorlab.com/guides/nist-password-guidelines/

> What NIST SP 800-63B-4 requires for passwords: 15-character minimum, no complexity rules or forced expiry, blocklists, and what changed from the 2017 version.

Updated 9 November 2026 · 7 min read

## Key takeaways

- NIST SP 800-63B-4 (2025) requires at least 15 characters for passwords used as the only login factor, and at least 8 when combined with another factor.
- Services must not impose composition rules or periodic password changes, but must force a change when there is evidence of compromise.
- New passwords must be checked against a blocklist of common, expected and breached passwords, and rejections must be explained.
- Services must allow password managers and autofill, limit failed attempts to 100 at most, and store passwords salted and hashed with a password-hashing scheme.
- Compared with the 2017 version, composition rules and forced expiry moved from 'should not' to 'shall not', and the single-factor minimum rose from 8 to 15.

Last reviewed 9 November 2026

NIST Special Publication 800-63B is the U.S. government's rulebook for how online services should authenticate people. It is written for federal agencies, but it has become the reference point for password policy almost everywhere: auditors cite it, vendors build their defaults around it, and other frameworks borrow from it. Revision 4 (SP 800-63B-4) was finalized in 2025 and tightened several rules that earlier versions only recommended.

This guide summarizes what it says about passwords, using NIST's own wording for how strict each rule is. In NIST documents, **SHALL** and **SHALL NOT** are requirements, **SHOULD** and **SHOULD NOT** are strong recommendations, and **MAY** is permitted.

## The password rules at a glance

| Rule | Strength | What it means in practice |
| --- | --- | --- |
| Minimum 15 characters when the password is the only factor | SHALL | A password-only login needs at least 15 characters. |
| Minimum 8 characters when the password is part of multi-factor authentication | SHALL (shorter than 15 is a MAY) | With a second factor, 8 is the floor. |
| Allow a maximum of at least 64 characters | SHOULD | Don't cap passwords at 16 or 20 — long passphrases need room. |
| Accept all printing ASCII characters and the space | SHOULD | No "symbols not allowed" errors; spaces are fine. |
| Accept Unicode, counting each code point as one character | SHOULD (counting: SHALL) | Accented letters and other scripts should work. |
| No other composition rules | SHALL NOT | No "one uppercase, one digit, one symbol" requirements. |
| No periodic password changes | SHALL NOT | No 60- or 90-day expiry. Force a change only on evidence of compromise (SHALL). |
| Check new passwords against a blocklist | SHALL | Reject common, expected and breached passwords, and say why. |
| No password hints or security questions | SHALL NOT | No hints visible before login, and no "first pet" prompts when choosing a password. |
| Allow password managers and autofill | SHALL | Don't block autofill; paste SHOULD work too. |
| Offer a "show password" option | SHOULD | Let people check what they typed. |
| Limit failed login attempts | SHALL | No more than 100 consecutive failures on one account before the password is disabled. |
| Store passwords salted and hashed with a password-hashing scheme | SHALL | Use a deliberately slow hash with a salt of at least 32 bits — never plain or fast hashes. |

## Length: 15 characters, or 8 with a second factor

The headline change in revision 4 is the length floor. Verifiers SHALL require passwords used as a single-factor authentication mechanism to be at least **15 characters**. They MAY allow shorter passwords when the password is only one part of multi-factor authentication, but never shorter than **8**. Services SHOULD let people use at least **64 characters**, and they SHALL check the whole password — no silently truncating it.

NIST's reasoning is that length is a primary factor in password strength, while composition rules add far less than they appear to. For a randomly generated password, each extra character multiplies the number of possibilities; see [How long should a password be?](https://passwordgeneratorlab.com/guides/password-length/) for the numbers.

## No composition rules, no forced expiry

Two long-standing habits are now explicitly forbidden. Verifiers SHALL NOT impose composition rules such as requiring a mix of character types, and SHALL NOT require people to change passwords periodically.

Both rules tend to make passwords more predictable, not less: people meet "one uppercase, one symbol" with `Password1!`, and meet a 90-day expiry by incrementing a number. The one exception matters, though: when there is **evidence that a password has been compromised**, the verifier SHALL force a change. Our guide [How often should you change your password?](https://passwordgeneratorlab.com/guides/how-often-should-you-change-your-password/) covers this in more detail.

## Blocklists instead of complexity

Instead of composition rules, NIST relies on screening. When someone sets or changes a password, the verifier SHALL compare the *entire* password against a blocklist of commonly used, expected or compromised values — for example, passwords from previous breaches, dictionary words, and context-specific words such as the service name or the username. If the password is on the list, the service SHALL require a different one and SHALL explain why.

NIST also notes that the list doesn't need to be enormous: it exists to stop passwords an attacker would try before hitting the rate limit, so an excessively large list adds little. Services SHALL also offer guidance to help people choose a strong password, especially right after a rejection, so they don't just tweak the rejected one.

You can see the same idea from the user side in our [leaked-password check](https://passwordgeneratorlab.com/password-strength-checker/#leak-check), which looks a password up in Have I Been Pwned's breach corpus without sending the password itself.

## Make good passwords easy to use

- **Password managers and autofill** SHALL be allowed, and paste SHOULD work when autofill isn't available. NIST notes that password managers — especially ones with built-in generators — make stronger passwords more likely.
- **Show password:** services SHOULD offer an option to display the password while it's being typed.
- **No hints and no security questions:** a hint visible to someone who isn't logged in is not allowed, and services SHALL NOT prompt people to use knowledge-based questions when choosing a password.
- **Typing allowances:** services MAY ignore leading and trailing spaces or the case of the first letter, as long as the result still meets the minimum length and isn't much weaker.

## Rate limiting and storage

Short passwords are only workable because guessing is throttled. Verifiers SHALL limit consecutive failed attempts on one account to **no more than 100**, after which the authenticator is disabled and has to be re-bound. Agencies may set lower limits, and NIST suggests techniques that reduce lockouts of legitimate users, such as increasing delays between attempts and bot-detection challenges.

On the server, passwords SHALL be salted and hashed with a suitable password-hashing scheme, with a salt of at least 32 bits. The cost factor SHOULD be as high as practical and SHOULD be raised over time. NIST also recommends (SHOULD) an extra keyed hashing step with a secret key stored separately from the password database, ideally in a hardware security module.

## What changed from SP 800-63B-3

The 2017 revision already moved away from complexity rules, but much of it was advice rather than a rule.

| Topic | 800-63B-3 (2017) | 800-63B-4 (2025) |
| --- | --- | --- |
| Name | "Memorized secrets" | "Passwords" |
| Minimum length (user-chosen) | 8 characters | 15 if the only factor; 8 with multi-factor authentication |
| Composition rules | SHOULD NOT | SHALL NOT |
| Periodic changes | SHOULD NOT | SHALL NOT |
| Password managers | Paste SHOULD be permitted | Password managers and autofill SHALL be allowed; paste SHOULD be |
| Guidance when choosing a password | SHOULD (e.g. a strength meter) | SHALL |
| Blocklist comparison | Against the list | Against the entire password, not substrings or words within it |

## How other frameworks compare

If your organization answers to more than one standard, these are the common differences:

- **PCI DSS v4.0** (payment-card environments) requires at least **12 characters** (8 if a system can't support 12), mandatory since 31 March 2025. Where a password is the only authentication factor, it must be changed at least every **90 days**, or account security must be analyzed dynamically instead. The PCI Security Standards Council confirms the 90-day rule doesn't apply where multi-factor authentication is used.
- **Microsoft 365** passwords never expire by default, and Microsoft's guidance labels "never expire" as the recommended setting for cloud-only accounts. Microsoft recommends a **14-character** minimum, although Microsoft 365 itself only requires 8.
- **The UK's NCSC** also advises against regular password expiry and recommends changing passwords when a compromise is known or suspected.

A policy that meets NIST — 15+ characters, a blocklist, multi-factor authentication — will usually satisfy the others too. The main exception is PCI DSS rotation for password-only access, which disappears once you add a second factor.

## A practical checklist

- Require 15+ characters for password-only logins, or 8+ when multi-factor authentication is enforced.
- Accept at least 64 characters, spaces, all printable ASCII and Unicode. Never truncate.
- Remove "must contain" rules and scheduled expiry.
- Screen new passwords against breached and common passwords plus your own context words, and explain rejections.
- Force a reset when you have evidence an account's password is compromised.
- Allow password managers, autofill and paste; add a "show password" toggle.
- Remove password hints and security questions.
- Limit failed attempts (100 at most) and store passwords with a salted, slow password hash.
- Turn on multi-factor authentication wherever you can.

Need a password that meets the NIST rules for a test account or a new user? The [password policy generator](https://passwordgeneratorlab.com/password-policy-generator/) has a NIST SP 800-63B-4 preset, and presets for Entra ID, Active Directory, AWS IAM, Google Workspace and PCI DSS.

## Sources

- [NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (2025)](https://pages.nist.gov/800-63-4/sp800-63b.html)
- [NIST SP 800-63B (2017): Digital Identity Guidelines — Authentication and Lifecycle Management](https://pages.nist.gov/800-63-3/sp800-63b.html)
- [PCI SSC: PCI DSS v3.2.1 to v4.0 Summary of Changes](https://listings.pcisecuritystandards.org/documents/PCI-DSS-v3-2-1-to-v4-0-Summary-of-Changes-r1.pdf)
- [PCI SSC FAQ: Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?](https://www.pcisecuritystandards.org/faqs/1590/)
- [Microsoft Learn: Password policy recommendations for Microsoft 365](https://learn.microsoft.com/en-us/microsoft-365/admin/misc/password-policy-recommendations)
- [NCSC: Password administration for system owners](https://www.ncsc.gov.uk/collection/passwords/updating-your-approach)

## Keep reading

- [WPA2 vs WPA3: which Wi-Fi security to choose](https://passwordgeneratorlab.com/guides/wpa2-vs-wpa3/) — WPA2-Personal vs WPA3-Personal explained: offline guessing, SAE, forward secrecy, mixed mode's downgrade risk, and the router settings to pick.
- [Password requirements by platform, compared](https://passwordgeneratorlab.com/guides/password-requirements-by-platform/) — Password rules side by side for NIST, Microsoft Entra ID, Active Directory, AWS IAM, Google Workspace, PCI DSS, GitHub, Apple, Salesforce and Oracle.
- [How often should you change your password?](https://passwordgeneratorlab.com/guides/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.
- [Passkeys vs passwords: what changes and what doesn't](https://passwordgeneratorlab.com/guides/passkeys-vs-passwords/) — How passkeys work, why they resist phishing, how they compare with passwords and 2FA, their limits, and why you still need strong passwords.
