Password Security•7 min read•

Corporate Password Policy Guide: Current Rules Based on NIST

How to write a corporate password policy: length, periodic changes, MFA and shared accounts per NIST SP 800-63B Rev. 4, with a step-by-step checklist.

What Is a Corporate Password Policy and Why Update It?

A corporate password policy is a formal document that sets the minimum criteria, management rules and security standards for the passwords people in an organization use to protect their accounts. Traditional policies are built on mandatory password changes at fixed intervals and complex character combinations. Today we know this approach falls short and can even weaken security.

The main reason to update is that attacks have changed. Beyond simple guessing, attackers now rely on dictionary attacks built from huge breach databases, credential stuffing with passwords stolen from other sites, and brute-force attacks on powerful GPUs. Old-style policies wear users out, so people write passwords on paper or reuse the same simple variation everywhere (Company2024!, Company2025!).

A modern policy should rest on length, breach checking and multi-factor authentication instead of rigid character rules.

Complexity or Length?

The traditional approach focuses on requiring certain character types. What actually matters is entropy: how random and how long a password is. Short but "complex" passwords fall quickly because of predictable patterns, while long passwords and passphrases made of random words are far more resistant.

You will find how current standards reflect this in the NIST section below.

Why Forced Periodic Changes Are Being Dropped

The "change your password every 90 days" rule is no longer recommended by NIST SP 800-63B; the current version asks verifiers not to force changes at fixed intervals. There are several reasons:

  1. Predictable variations: users forced to change usually just increment the last digit (Password1 → Password2). An attacker who has the old password can easily guess the new one.
  2. Weaker passwords: frequent mandatory changes push users toward simpler, easier-to-remember passwords.
  3. Operational load: reset requests needlessly increase the IT team's workload.

The new approach: change a password only when there is suspicion of a breach or evidence of compromise, and in that case make the change mandatory. A stable but strong password is safer than weak passwords that keep changing.

Password Requirements According to NIST SP 800-63B

The current version of NIST SP 800-63B (Revision 4, 2025) sets these principles for passwords:

Topic Old approach (avoid) Current NIST approach
Change frequency Forced change every 30/60/90 days Change only on evidence of breach or compromise
Character rules Required uppercase + digit + symbol No character-type rules; length is what counts
Minimum length Often 8 characters At least 15 for passwords used alone, at least 8 when part of MFA
Maximum length Short upper limits Allowing at least 64 characters is recommended
Checks Rule compliance only Comparison against breached and common password lists
Hints Password hints, security questions No hints or security questions; password managers are supported

Recommendation: set the minimum length to 15 characters for accounts without MFA, allow spaces and long passphrases, and block passwords such as "123456", "password" or ones containing your company name.

The Role of MFA in Corporate Accounts

Even the strongest password can be stolen in a phishing attack. Multi-factor authentication (MFA) is the second line of defense. It asks for proof from different categories at sign-in:

  • Something you know: a password or PIN.
  • Something you have: a code from an authenticator app (TOTP), a physical security key (FIDO2) or a passkey.

An SMS code is better than nothing, but NIST classifies SMS as a "restricted" method because it is exposed to attacks such as SIM swapping. Prefer an authenticator app or a FIDO2 key where possible; FIDO2 keys and passkeys are the most phishing-resistant options.

In a corporate environment, MFA on VPN, email and admin panels should be mandatory, not optional. With MFA enabled, an attacker who steals a password has a much harder time getting into the account.

Managing Shared Accounts and Their Risks

Some teams use shared accounts such as a "common social media account" or a "general admin account". This carries serious risks:

  • Loss of accountability: you cannot tell who made a mistaken or malicious change.
  • Staff departures: someone who leaves keeps knowing the shared password.
  • Spreading leaks: once a shared password leaks, everyone's access is at risk.

Solution: give each employee an individual account where possible and grant permissions through role-based access control (RBAC). If shared use is unavoidable, share the password through a corporate password manager and change it immediately when someone leaves the team or a leak is suspected.

Employee Awareness and Password Managers

However strong the technology, the weakest link is often human. To build a security culture:

  1. Phishing training: teach employees how to recognize fake emails.
  2. Password managers: the human brain is not built to remember dozens of different, long passwords. Encourage tools such as Bitwarden or KeePassXC to break the habit of reusing one password everywhere.
  3. Simple guides: share short, visual "how to create a strong password" guides instead of complex technical documents.

Step-by-Step Corporate Password Policy Checklist

  • Analyze the current state: what are your length limits today, and how often are changes required?
  • Set the minimum length: at least 15 characters for accounts without MFA and at least 8 for accounts with MFA (NIST). Use longer passwords and mandatory MFA for admin accounts.
  • Remove character-type rules: base the policy on length instead of requirements like "at least one symbol".
  • Remove forced periodic changes: switch from calendar-based changes to event-based changes (breach, suspicion).
  • Roll out MFA: enable multi-factor authentication on every critical sign-in point.
  • Create a blocklist: block your company name, city names and common passwords seen in breaches.
  • Provide tools: announce a password manager and a password generator employees can use to create random passwords.
  • Document and announce: write the new rules in plain language and share them with every employee.

Frequently Asked Questions

Is it safe never to change passwords? Routine changes at fixed intervals (for example every 3 months) are not recommended, but a password must be changed immediately when there is any sign of a breach or suspicion that someone else knows it.

Do special characters still matter? They should not be mandatory. NIST asks verifiers not to impose character-type rules; length is what really counts. A symbol in a randomly generated password adds entropy, but it should not be forced on users as a rule.

What is a passphrase? A long password made of unrelated words placed side by side (for example blue-melon-bicycle-cloud): easy to remember, hard to crack.

Do I still need a strong password if I use MFA? Yes. MFA is a very strong layer, but some attacks such as session hijacking can get around it. A strong password remains the first line of defense.

To create secure, random passwords, use our free password generator, which runs entirely in your browser and never sends any data to a server.

Generate Strong Credentials Instantly

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

Open Password Generator →