Password Policy for Small Businesses: A Simple 2026 Checklist

Many small businesses still use password rules written ten years ago: change every 90 days, at least one capital letter, one number and one symbol. Current guidance, including the US NIST digital identity guidelines (SP 800-63B), now says most of these rules make security worse. People respond with predictable patterns like Summer2026! and sticky notes. Here is what to do instead.

The checklist

1. Length over complexity

  • Require at least 15 characters for passwords that are used on their own, and at least 8 when the account also has multi-factor authentication.
  • Allow up to at least 64 characters, and allow spaces, so staff can use passphrases.
  • Drop “must contain a symbol and a number” rules. Length does far more. See why in our guide to password length vs complexity.

2. Block known-bad passwords

Instead of composition rules, reject passwords that appear in breach lists, dictionary words, the company name and obvious patterns like 12345678. Staff can check a password themselves with our Password Breach Checker, which never sends the password anywhere.

3. No forced periodic resets

Only require a change when there is a reason: a breach, a phishing incident, a staff member leaving, or a password found in a leak. Scheduled resets just produce Password1, Password2, Password3.

4. One password per account, stored in a manager

Password reuse is the biggest risk for small teams. Give everyone a password manager or vault and make it the only allowed place to store passwords. Generate new ones with the Advanced Password Generator or, for things people must type, the Passphrase Generator.

5. Multi-factor authentication everywhere it matters

Turn on MFA for email, accounting, banking, cloud storage, your website admin and domain registrar. Prefer passkeys or authenticator apps over SMS. Email and the domain registrar come first: whoever controls them controls the business.

6. Never share passwords over chat or email

Shared logins happen. When they do, share them through the password manager, or with a self-destructing encrypted message, never in WhatsApp groups, spreadsheets or email threads that live forever.

7. Allow paste and password managers

Login forms that block pasting push people toward short passwords they can type. Make sure your own website and internal tools allow paste and autofill.

8. Store passwords correctly (for your developers)

If your business runs its own app or website, passwords must be stored with a slow, salted hash such as bcrypt or Argon2, never in plain text or with MD5/SHA-1. WordPress 6.8 and later uses bcrypt by default. Developers can test hashes with our Bcrypt Generator & Checker.

9. Offboarding

When someone leaves, disable their accounts the same day and change every shared password they knew. A password manager with shared folders makes this a ten-minute job instead of a guessing game.

10. Five-minute training

Teach staff three habits: never log in from links in messages, never share codes or passwords with callers, and report anything suspicious quickly without fear of blame. Our guide on spotting fake login pages is a good start.

A ready-to-use policy paragraph

All company accounts use unique passwords of at least 15 characters, generated and stored in the company password manager. Passwords are changed only when there is evidence of compromise. Multi-factor authentication is required for email, finance, cloud and admin accounts. Passwords and one-time codes are never shared by email or chat.

FAQ

Is it really OK to stop forcing password changes?
Yes, as long as passwords are long, unique, checked against breach lists and protected with MFA. Change them immediately when there is any sign of compromise.

What about compliance rules that still ask for rotation?
Follow what your auditor requires, but you can usually reduce the frequency if you show MFA, breach screening and a password manager are in place.

Menu