Skip to content
Bellator Cyber Guard
Learn22 min readDeep Dive

Password Security Best Practices: Beyond Complex Passwords

Compare passwords, password managers, MFA methods, and passkeys using current NIST SP 800-63B-4 guidance. Length beats complexity. See what to enable first.

By Bellator Cyber Guard Security Team
Password Security Best Practices: Beyond Complex Passwords - password security best practices

Editor's note (updated August 2026): This guide has been reviewed against the current NIST digital identity standard, SP 800-63B-4, finalized in 2025. The password, MFA, and passkey recommendations below reflect that guidance.

The strongest password security best practices in 2026 come down to three moves: make passwords long instead of complex, stop forcing scheduled resets, and protect every account with a password manager plus multi-factor authentication (MFA).

For decades the standard advice was to mix uppercase, lowercase, numbers, and symbols, change passwords every 90 days, and never write them down. Research from the National Institute of Standards and Technology (NIST), Microsoft, and the Cybersecurity and Infrastructure Security Agency (CISA) shows that guidance is now outdated and often counterproductive. This guide compares the methods that actually protect accounts and shows what to do first, whether you secure personal logins or an organization's authentication systems.

NIST Special Publication 800-63B is the U.S. government's Digital Identity Guidelines, the authoritative reference for how passwords should be created, stored, and verified. The 2025 revision, SP 800-63B-4, keeps the core shift in place: length beats complexity, forced rotation does more harm than good, and a password manager paired with MFA is the foundation every account should rest on.

Quick Answer

Prioritize length over complexity: aim for 12-16 character passphrases, not forced symbol combinations. Do not rotate passwords on a fixed schedule; change them only when a breach or suspicious activity is detected. Use a password manager to generate and store a unique password for every account, screen new passwords against known breached credentials, and require multi-factor authentication on anything holding sensitive data. Enable passkeys wherever they are offered.

Password Security by the Numbers

850M+
Breached passwords on record in the Have I Been Pwned dataset
38%
Year-over-year rise in credential stuffing reported in the 2025 Verizon DBIR
16+
Characters recommended for a strong passphrase

Why the Old Password Rules Failed

Traditional password policies were well intentioned, but they produced predictable human behavior that attackers learned to exploit. Understanding why they failed is the first step to replacing them.

Forced complexity led to predictable patterns. When required to add an uppercase letter, a number, and a symbol, people reliably created passwords like 'Password1!' or 'Summer2026!' that met every technical rule yet were trivial to guess. Carnegie Mellon University research found that strict composition rules increased predictability rather than reducing it.

Frequent changes encouraged weaker passwords. Forced to rotate every 60 or 90 days, users made minimal edits: Password1 becomes Password2 becomes Password3. A University of North Carolina study found that 17% of new passwords could be guessed from old ones in fewer than five attempts.

'Don't write it down' led to reuse. Unable to remember dozens of unique strings, people reused one password across email, banking, and work systems. Credential stuffing is an attack where criminals replay username and password pairs stolen from one breach against many other sites. According to the 2025 Verizon Data Breach Investigations Report, credential stuffing rose 38% year over year. The same attack pattern feeds the AI-assisted phishing attacks now hitting inboxes at scale.

Length was undervalued. A 12-character password with mixed case, numbers, and symbols holds roughly 72 bits of entropy. A 20-character all-lowercase password holds about 94 bits, far stronger, yet old policies rejected it as not complex enough. When researchers examined credentials exposed in the LinkedIn, Adobe, and Yahoo breaches, users under stricter policies did not have more secure passwords. They had more predictable ones.

The Password Paradox

Rules designed to force strong passwords often produce weak, predictable ones. Complexity mandates and 90-day rotation push people toward guessable patterns and reuse. Length, uniqueness, and breach screening protect an account far more than character variety ever did.

Modern Password Guidance: NIST SP 800-63B

NIST SP 800-63B is a set of Digital Identity Guidelines that defines how organizations should handle authentication, and it is the authoritative password reference for 2026. Its core recommendations reverse much of the old advice.

Prioritize length over complexity. NIST sets a minimum of 8 characters for user-created passwords but strongly encourages 12-16 or more. A passphrase such as 'correct horse battery staple' is far stronger than 'P@ssw0rd!'.

Eliminate mandatory expiration. NIST explicitly states passwords should not be changed on an arbitrary schedule. Rotate only when there is evidence of compromise.

Allow password pasting. Login fields must accept pasted text, which enables password manager adoption, the single most effective improvement most people can make. If you are choosing a tool, our guide to the best password manager for personal use walks through the options, and NIST's position is summarized in our NIST password manager recommendation explainer.

Screen against breached passwords. New passwords should be checked against databases of compromised credentials, such as the Have I Been Pwned Pwned Passwords set of more than 850 million entries. The API supports this check without exposing the password being tested.

Remove composition rules. Allow any printable ASCII and Unicode, including spaces, so users can build long, memorable passphrases.

Require multi-factor authentication. MFA is a control that requires two or more independent proofs of identity before granting access. NIST calls for MFA on any account that reaches sensitive data or systems, because even the strongest password can fall to phishing, malware, or insider threats. Microsoft has reported that after enabling breach-password detection and removing forced expiration, password-related support tickets fell sharply and account compromise dropped, because users stopped cycling through predictable variants.

NIST SP 800-63B Implementation Checklist

  • Set minimum password length to 12-16 characters (8 minimum for legacy systems)
  • Eliminate mandatory 90-day password rotation policies
  • Enable password pasting in all login fields and forms
  • Screen new passwords against the Have I Been Pwned breach database
  • Remove arbitrary uppercase, number, and symbol requirements
  • Allow all printable characters, including spaces, in passwords
  • Require multi-factor authentication for all sensitive system access
  • Change passwords only when compromise is detected or suspected

Passkeys: The Future of Authentication

A passkey is a login credential built on public-key cryptography that replaces the password entirely. Passkeys use the FIDO2 and WebAuthn standards from the FIDO Alliance, an industry body that develops open authentication standards. Instead of a shared secret, your device holds a private key that never leaves it, and the server holds only the matching public key. When you sign in, your device signs a challenge with the private key, proving your identity without transmitting any secret.

Why Passkeys Outperform Passwords

Phishing-resistant by design. A passkey is cryptographically bound to a specific domain, so it will not work on a fake site impersonating your bank. Google has reported that passkeys eliminated phishing for employees who adopted them.

Unguessable and unique. Each passkey is a unique key pair, typically based on 256-bit elliptic-curve cryptography. There are no dictionary words to guess and no credential database to crack.

Fast and convenient. Authentication uses biometrics or your device PIN. In Google's studies, passkeys signed users in roughly four times faster than passwords, with a higher success rate.

Synced across devices. Apple iCloud Keychain, Google Password Manager, and Microsoft tools sync passkeys with end-to-end encryption, so the private keys stay under your control. As of 2026, passkeys work across iOS 16+, macOS Ventura+, Android 9+, and Windows 11, and Google, Microsoft, Apple, PayPal, Amazon, and GitHub all offer passkey sign-in. When a service supports a passkey, make it your first choice.

Why choose a passkey

  • Domain-bound cryptography that a phishing site cannot capture or replay
  • No shared secret stored on the server, so a database breach exposes nothing usable
  • Faster sign-in with a fingerprint, face scan, or device PIN
  • Nothing for the user to remember, type, or reuse

What to plan for

  • Not every site or app supports passkeys yet, so passwords remain the fallback
  • Recovery depends on your synced ecosystem, so keep a backup method like an authenticator app
  • Account sharing and shared workstations need planning before you switch

How to Set Up Passkeys

1

Check device compatibility

Confirm your device runs iOS 16+, macOS Ventura+, Android 9+, or Windows 11 and that biometrics or a device PIN is enabled.

2

Open account security settings

Sign in to a service that supports passkeys, such as Google, Microsoft, Apple, GitHub, or PayPal, and find the passkey or security key option.

3

Create the passkey

Select 'Create a passkey' and confirm with your fingerprint, face scan, or device PIN. The private key is generated and stored on your device.

4

Confirm cross-device sync

Verify the passkey syncs through iCloud Keychain, Google Password Manager, or your password manager so it is available on your other devices.

5

Sign in with the passkey

Test the new passkey on your next login and keep a backup method, such as an authenticator app, until passkeys cover all your key accounts.

Multi-Factor Authentication: Your Safety Net

Even the best password habits cannot stop every compromise. Passwords get phished, stolen by malware, exposed in breaches, or extracted through social engineering. MFA ensures a stolen password alone cannot open your account. It combines two or more independent factors:

  • Something you know: a password, PIN, or security question
  • Something you have: a phone, hardware token, or smart card
  • Something you are: a fingerprint, face, or voice pattern

The strength of MFA depends heavily on the second factor. Some methods can be phished or socially engineered, while others give cryptographic guarantees that defeat those attacks. Use the comparison below to match the method to the value of the account.

What to Ask Before Choosing a Password Manager

  • Does it check new and stored passwords against known breach databases?
  • Does it generate and store passkeys, not just passwords?
  • Does it use zero-knowledge, end-to-end encryption so the vendor cannot read your vault?
  • Does it work across your phones, laptops, and browsers without extra cost?
  • Does it support secure sharing and, for teams, admin recovery and access controls?
  • Has the vendor published independent security audits and clear breach history?

Compare the tools before you commit

See how leading options score against the criteria above so you pick one that fits your accounts and budget.

Get Your Free Cybersecurity Evaluation

Talk through your password, MFA, and account protection setup with a specialist and get a clear plan for closing the gaps.

Frequently Asked Questions

Share

Share on X
Share on LinkedIn
Share on Facebook
Send via Email
Copy URL
(800) 492-6076

People also look for

Keep exploring Passwords & account security

Make passwords, password managers, MFA, and passkeys work together to reduce account takeover risk.

Learn first. Decide when you are ready.

Build a practical account-security baseline

Connect password managers and MFA with safe recovery, privileged access controls, monitoring, and a clear response process.