Password Security•8 min read•

How to Create a Strong Password: NIST SP 800-63B Guide

Learn how to create cryptographically resilient passwords based on NIST SP 800-63B guidelines prioritizing length over arbitrary complexity.

Introduction: The End of Legacy Password Rules

For decades, corporate IT policies and websites enforced the same rule: "Use at least 8 characters with one uppercase letter, one lowercase letter, one digit and one symbol, and change it every 90 days."

On paper this widens the character pool, but in practice it collided with human psychology. To cope with rules they could not remember, people fell back on predictable patterns: capitalising the first letter, appending "1!" (for example London2024!) and bumping the last digit every quarter (London2025!).

In 2017 the US National Institute of Standards and Technology (NIST) published NIST Special Publication 800-63B: Digital Identity Guidelines, which overturned this decades-old approach. Modern application security now rests on one clear principle: length beats artificial complexity.


Core Principles of NIST SP 800-63B

NIST studied how attackers actually crack passwords and made the following recommendations for modern authentication:

1. Stop Enforcing Arbitrary Composition Rules

Forcing symbols and digits pushes users towards predictable substitutions (leetspeak: '@' for 'a', '3' for 'e'). Cracking tools such as Hashcat and John the Ripper already ship these substitutions in their default rule sets. Instead of mandating character types, raise the minimum length.

2. Aim for a Minimum of 15-16 Characters

The current revision of the guideline requires at least 15 characters when a password is the only authentication factor, and accepts 8 characters only when it is combined with multi-factor authentication. Even with the full 88-character pool our generator uses (or the theoretical 94 printable ASCII characters), an 8-character password has only about 51.7 bits of entropy (52.4 bits with 94 characters), which a GPU cluster can exhaust in hours. A 20-character password made only of lowercase letters (262026^{20} combinations) is far stronger than a 10-character password drawn from all 88 characters.

3. Remove Forced Periodic Password Changes

Making users change passwords every 30, 60 or 90 days does not improve security; it weakens it. Users who are forced to rotate passwords create weaker variations or write them down. Under NIST guidance, a password should be changed only when there is evidence or suspicion of compromise.

4. Block Passwords That Have Already Been Breached

Systems should compare a newly chosen password against known breach corpora such as Have I Been Pwned and reject passwords that have already been exposed.

5. Drop Password Hints and Security Questions

Questions such as "What is your mother's maiden name?" or "What was your first pet called?" can often be answered within minutes through social media and open-source intelligence (OSINT). They are the weakest link in the authentication chain.


The Maths: Length vs Complexity

In information theory, entropy measures how unpredictable a password is, expressed in bits:

Entropy=L×log⁡2(N)\text{Entropy} = L \times \log_2(N)

Here LL is the password length and NN is the size of the character pool. The examples below assume an offline attacker testing 101110^{11} (100 billion) guesses per second against a fast hash such as NTLM or MD5, which is roughly what a single high-end GPU achieves.

  • Scenario A (legacy rule): 8 characters from a complex pool (upper + lower + digits + symbols = 88 characters; theoretical 94 ASCII). Entropy=8×log⁡2(88)≈8×6.46=51.7 bits\text{Entropy} = 8 \times \log_2(88) \approx 8 \times 6.46 = 51.7 \text{ bits} The whole keyspace of 251.72^{51.7} combinations is exhausted in about 10 hours, and on average the password falls in half that time.

  • Scenario B (NIST / Diceware approach): a 5-word passphrase from a 4,096-word list. Entropy=5×log⁡2(4096)=5×12.0=60.0 bits\text{Entropy} = 5 \times \log_2(4096) = 5 \times 12.0 = 60.0 \text{ bits} It is 18-22 characters long, easy to remember, and exhausting it at the same rate takes about four months.

  • Scenario C (modern standard): 16 characters generated with a CSPRNG from our 88-character pool. Entropy=16×log⁡2(88)≈16×6.46=103.4 bits\text{Entropy} = 16 \times \log_2(88) \approx 16 \times 6.46 = 103.4 \text{ bits} That is 2103.42^{103.4} (about 1.4×10311.4 \times 10^{31}) combinations: far beyond the reach of any brute-force attack for the foreseeable future.


Golden Rules for Strong Passwords

  1. A unique password for every account: Never reuse a password across two services. When one site is breached, attackers automatically try the same email and password on banks, email providers and shops (credential stuffing).
  2. Use cryptographic randomness: The human brain is bad at producing randomness. Use a trustworthy in-browser generator built on the Web Crypto API and create random strings of at least 16 characters.
  3. Use a password manager: Do not try to memorise 100 different 16-character passwords. Use an end-to-end encrypted manager such as Bitwarden, 1Password or KeePassXC.
  4. Turn on multi-factor authentication (2FA / passkeys): However strong your password is, enable FIDO2/WebAuthn or TOTP-based 2FA to protect against phishing and session theft.

Generate Strong Credentials Instantly

Hardware-backed Web Crypto API with zero logging and zero server contact.

Open Password Generator →