Write a password policy that reflects current guidance, not 2005.
12 characters gives about 56 bits of entropy
The current guidance from both NIST and the UK NCSC points the same way: length matters, checking against known breached passwords matters, and forced complexity rules and periodic expiry make things worse rather than better. Expiry in particular pushes people to increment a digit, which is a pattern an attacker exploits rather than one it defeats. The one thing that outweighs everything on this page is not the policy at all. Adding a second factor blocks the credential-stuffing attacks that use passwords already known to be valid.
• At least 12 characters. Longer is better, and length beats complexity at every size. • Up to 128 characters accepted, with no restriction on which characters may be used. • Checked against a list of known breached and common passwords, and rejected if found. • No mandatory periodic expiry. Passwords are changed when there is a reason to believe one is compromised. • Spaces and pasting are allowed, so password managers work.
^(?=.*[a-z]).{12,128}$What this cannot tell you
Take this with you
This tool never saves runs. What it handles should not be written to disk — not even your own.
Password Policy Generator on RunTheTests — free browser-based websec tools, no sign-up.