Course contentsShow
← Computer Science
Lesson 2512 of 2,87256. Authentication and AuthorizationFree lesson

Password Policies and Requirements

Designing effective password policies: length, complexity, and avoiding counterproductive rules.

Password Policies and Requirements

What you'll learn: How to design password policies that genuinely improve security without frustrating users or creating counterproductive behavior.

The Challenge of Policy Design

After implementing strong password hashing (bcrypt, Argon2) and understanding entropy, organizations must decide: what rules should govern password creation? This is surprisingly tricky. Overly strict policies often backfire, leading users to write passwords down, reuse them across sites, or use predictable patterns like Password1!, Password2!, etc.

Effective Password Requirements

Length Over Complexity

The single most important factor is length. A 16-character password made of random words (correct-horse-battery-staple) has far more entropy than P@ssw0rd! despite lacking special characters. Modern guidance recommends:

  • Minimum 8-12 characters (ideally longer)
  • No maximum length (within reason, like 128 characters)
  • Length dramatically increases the search space for attackers

Sensible Complexity Rules

If you require complexity, keep it simple:

  • Mix of uppercase and lowercase helps
  • Numbers and symbols add entropy but don't force rigid patterns
  • Avoid requiring "at least one uppercase, one number, one symbol" — this creates predictable patterns

Counterproductive Rules to Avoid

  1. Mandatory password rotation (changing every 60-90 days): Research shows this encourages weak, incremental changes
  2. Blocking dictionary words entirely: Prevents strong passphrases like Blue-Mountain-Coffee-Morning
  3. Overly restrictive character rules: Reduces possible password space

The Human Factor

Think of password policies like building codes: too lax and the structure is unsafe; too strict and builders cut corners. The goal is usable security — policies strong enough to resist bcrypt/Argon2 cracking attempts but practical enough that users comply honestly.

Key Takeaway: Effective password policies prioritize length, check against breached password databases, and avoid counterproductive complexity requirements that encourage predictable patterns or written-down passwords.