Set a minimum length of at least 14 characters, with 16 or more preferred, and require randomness over predictable patterns. Complexity helps, but length is the stronger driver of resistance to brute-force attacks. Teams should also allow passphrases where policy permits, avoid personal information, and pair password rules with rate limiting and multifactor authentication to reduce the impact of compromise.
What password length should organisations standardise on?
Length should be the primary requirement because it raises the cost of brute-force guessing more reliably than character-class complexity rules. A practical standard is a minimum of 14 characters, with 16 or more preferred for most user accounts. Longer passwords also work better with passphrases, which can improve memorability without weakening resistance.
That same principle is why modern policies usually avoid over-focusing on composition rules like “must include a symbol” unless there is a specific system constraint. Predictable patterns such as seasonal words, keyboard walks, or reused templates reduce the security benefit of length and make user behaviour easier for attackers to anticipate. NHIMG’s Password Security and Password Manager Guide covers the modern policy direction, and NIST SP 800-63 Digital Identity Guidelines supports the broader shift toward longer secrets and away from rigid composition-only rules.
For organisations that still need complexity requirements, treat them as a secondary control, not the main defence. Complexity can help reduce reuse of common patterns, but the real value comes when the policy permits genuinely random strings or well-formed passphrases rather than forcing users into awkward substitutions that are easy to guess and hard to remember.
How should complexity rules be written without making passwords worse?
Complexity rules should be simple enough to avoid predictable workarounds. If your policy mandates uppercase, lowercase, numbers and symbols, users often respond with repeatable patterns, which can create the appearance of strength without much real gain. A better standard is to allow broad character sets, accept long passphrases, and avoid rules that force trivial substitutions or unnecessary renewal cycles.
One useful test is whether a policy produces stronger secrets in practice or merely more user frustration. If users are forced to add a symbol at the end of a familiar base word, the control may be easy to audit but weak in reality. If the policy allows random generation or multi-word passphrases, it usually gives better protection and better adoption at the same time.
The strongest policy language is usually outcome-based: require secrets that are long, hard to predict, and not derived from personal information, dictionary words in obvious order, or reused organisation templates. Password Policy Guide (NIST-aligned) gives a practical model for writing and enforcing that standard, while OWASP Top 10 A07 Guide is useful when you want to understand how authentication failures show up in real systems.
What should accompany password standards so they actually reduce risk?
Password policy alone is not enough because the main failure mode is not just guessing, it is account compromise through reuse, phishing, stuffing, and exposed credentials. Organisations should pair length and complexity rules with rate limiting, breached-password screening, and multifactor authentication so that a single weak or stolen password does not become immediate access.
This is also where account governance matters. A strong standard is undermined if privileged accounts, shared accounts, or service credentials follow different rules without compensating controls. CIS Control 5 Account Management Guide is useful for the inventory and review side of that problem, and Password Policy Template is a practical reference when teams need a complete policy baseline that includes breached-password screening, MFA, and account-specific handling.
Risk and Threat Considerations
Poor password standards create both operational and adversarial risk. Short or predictable passwords are easier to brute force, easier to spray at scale, and more likely to be reused across systems, which turns one exposed account into a broader compromise path. Weak policy also increases help desk resets and encourages unsafe user workarounds.
Failure mechanism: Attackers exploit low-entropy or reused passwords through guessing, spraying, credential stuffing, or recovery abuse, then pivot into the account when the organisation has no effective rate limit, MFA, or breach screening.
Impact: The result can be account takeover, lateral movement, unauthorised data access, and a much larger blast radius if the compromised account has elevated access or access to shared systems.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, CIS Controls v8, OWASP ASVS and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Covers password length, memorability, and modern authenticator guidance. |
| Recommendation — Adopt longer secrets and allow passphrases instead of relying on rigid composition rules. | ||
| CIS Controls v8 | CIS-5 — Account Management | Account inventories and review support consistent password policy enforcement across accounts. |
| Recommendation — Inventory all accounts and apply password standards consistently across privileged and ordinary users. | ||
| OWASP ASVS | V6 — Authentication | Authentication verification includes password policy strength and login protection requirements. |
| Recommendation — Validate password rules, throttling, and MFA as part of authentication design. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Authenticator lifecycle control directly covers password policy, complexity, and change handling. |
| IA-2 — Identification and Authentication (Organizational Users) | User account authentication depends on strong password standards for organizational users. | |
| Recommendation — Manage password authenticators with lifecycle controls that reduce guessing and reuse risk. Require strong user authentication settings for all organizational accounts. | ||
Practitioner Guidance
What to prioritise: Make length the default control and use complexity only where a specific system constraint demands it. A 14-character minimum is a sensible floor for most user accounts, with 16 or more preferred when the user base and application stack can support it.
What to verify: Check that your policy actually allows passphrases, does not force brittle character substitution patterns, and is enforced consistently across SSO, legacy applications, and local account stores. Also verify that breached-password screening and rate limiting are active, because those controls do more real work than extra symbol requirements.
Decision rule: If the policy creates memorisable but predictable passwords, redesign it. If it creates long, random, or passphrase-based secrets and is paired with MFA, it is usually doing the right job.
Practitioner takeaway: The best password policy is the one users can follow without inventing shortcuts, while still making brute force and reuse unattractive to attackers.
Related resources from NHI Mgmt Group
- When should organisations prioritise password length over composition complexity?
- How should students and early career users set up password hygiene across school, personal, and travel accounts?
- How should security teams implement strong password generation across user accounts and service access points?
- What breaks when password rotation is still done manually across end-user, admin, and service accounts?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org