Skip to content
←Back to glossaryCyber

Password policy

The rules an organization sets for passwords (length, composition, lifetime, rejection of known-breached ones); a cyber underwriter assumes they will leak and looks at what backs them up.

Definition

A password policy is the set of rules an organization applies to its account passwords: minimum length, composition, lifetime, rejection of known-compromised passwords, lockout after a run of failed attempts. The doctrine flipped in 2017. The NIST (National Institute of Standards and Technology) Special Publication SP 800-63B stopped recommending forced periodic changes and composition rules (one uppercase letter, one digit, one symbol), which produced Spring2024! followed by Summer2024!. Instead it calls for adequate length and for checking every new password against a list of known-breached ones. Its next revision prohibits requiring periodic changes absent evidence of compromise. The password on Colonial Pipeline's VPN account in May 2021 had, according to Mandiant, turned up in a batch of leaked passwords. The cyber questionnaire seldom asks about the policy itself. It assumes the password will leak, through phishing, an infostealer or credential stuffing, and asks what happens next: MFA (multi-factor authentication), lockout, sign-in monitoring. When it does come back to passwords, it is on specific points: minimum length for privileged accounts, default passwords on equipment, a password manager for the IT team, unique local admin passwords. Those answers are hard to verify from outside. The underwriter cross-checks against known leaks, and employee credentials found in recent infostealer logs contradict a "compliant policy" better than any interview. A practitioner's caveat: an Active Directory policy that looks flawless on paper often leaves untouched the service accounts created before it, with a password that never expires and that nobody dares to change.

Its 7 cross-references, woven across the glossary's 18 categories
Password policy: Cyber glossary illustration, AlgoPolis
Example

Textbook case, made-up figures: an insured with 1,200 accounts declares a 12-character minimum and rotation every 90 days. The underwriter's threat feed turns up 46 employee username and password pairs in infostealer logs less than six months old. If 10% are still valid, 4 or 5 accounts are open to whoever buys them. Everything then rides on MFA: behind it, those accounts give up only a password; without it, they give up access. The underwriter asks for the 46 accounts to be reset and for proof of MFA on email before quoting.

Read next
Put it to work
Related terms
Also known as

password policy, password rules, password complexity requirements, banned password list

Stay informed

Follow the research

One letter a week. First, the week's underwriting note, when one is published: a dated, argued decision, signed by Paul Bernardski. Then what the observatory published on cyber risk, political risk and insurance. No account, no tracking.

No spam, one-click unsubscribe, no data ever sold.