Password Policy Checker
Assess your organisation's policy against NIST SP 800-63B-4 and OWASP guidance. Free, no login, no password required.
Quick answer
Describe your password rules to compare them with NIST SP 800-63B-4 and relevant OWASP authentication guidance. The assessment checks length, MFA coverage, composition, expiry, screening, password-manager support, hints and throttling locally in your browser. Each finding cites a verified section. Copy the proposed policy for review; results are not compliance certification.
Verified guidance
NIST SP 800-63B-4 §3.1.1.2 covers password verifiers. §3.2.2 covers throttling; §2.1 and §2.2 provide MFA context.
Also review OWASP password strength controls and login throttling. Sources checked November 16, 2026. NIST requirements and recommendations are distinguished in each finding.
Frequently asked questions
Which NIST revision does this checker use?
It uses NIST SP 800-63B-4, the current fourth revision, checked on November 16, 2026. Password rules are in section 3.1.1.2, MFA context in sections 2.1 and 2.2, and rate limiting in section 3.2.2. OWASP Authentication Cheat Sheet supplies complementary implementation guidance.
What minimum password length does NIST require?
Section 3.1.1.2 requires at least 15 characters when a password is used as a single factor. A minimum of 8 is permitted when the password is only used as part of MFA. Optional MFA does not make the shorter minimum appropriate for accounts that can still sign in with a password alone. NIST recommends supporting a maximum length of at least 64 characters.
Should we require symbols and regular password changes?
Section 3.1.1.2 prohibits character-mixture rules and scheduled password changes. It requires forcing a change when there is evidence of compromise. Check the whole prospective password against common, expected or compromised values at creation or change instead of relying on composition rules.
Should we allow password managers and paste?
NIST section 3.1.1.2 requires allowing password managers and autofill and recommends permitting paste when autofill APIs are unavailable. OWASP Authentication Cheat Sheet also recommends allowing paste. A policy should support these workflows rather than force users to type every secret manually.
Does an aligned result certify compliance?
No. Findings describe only the answers you enter. This tool does not inspect your identity system, verify MFA quality or determine your required assurance level. Review hashing, transport security, recovery, Unicode handling, session management and implementation evidence separately. Partial alignment can indicate an unmet recommendation or incomplete coverage.
Do I need to enter a password or upload policy data?
No. Enter policy settings only, never a real password. Assessment and draft generation run in your browser, and your answers are not uploaded or saved. Usage analytics receive the tool name only. Copying the proposed policy requires an explicit action.