Course contentsShow
← Software Engineering
Lesson 1004 of 1,93331. Authentication and AuthorizationFree lesson

Password Strength Requirements and Policies

Designing effective password policies that improve security without creating usability problems or encouraging bad practices.

Password Strength Requirements and Policies

What you'll learn: How to design password policies that actually strengthen security without frustrating users or encouraging risky workarounds.

The Challenge of Policy Design

Now that you understand hashing, salting, and work factors from previous lessons, we need to address what happens before a password enters your system. Password policies define the rules users must follow when creating passwords — but poorly designed policies can backfire spectacularly.

Common Requirements and Their Trade-offs

Traditional password policies often mandate:

  • Minimum length (e.g., 8-12 characters)
  • Character variety (uppercase, lowercase, numbers, symbols)
  • Expiration periods (force changes every 90 days)
  • History rules (can't reuse last 5 passwords)

The problem? Complex requirements often lead to predictable patterns like Password1!, Password2!, Password3! — technically compliant but easily crackable. Forced expiration encourages users to make minor, predictable modifications or write passwords down.

Modern Best Practices

Research-backed approaches emphasize:

Length over complexity: A 16-character passphrase like correct-horse-battery-staple is exponentially stronger than P@ssw0rd! and easier to remember.

Minimum 8-12 characters, but encourage longer passphrases without arbitrary maximum limits.

Screen against known breached passwords: Check new passwords against databases of compromised credentials (like HaveIBeenPwned).

Eliminate forced expiration unless breach suspected — it causes more harm than good.

Allow all printable characters including spaces to support passphrases.

Think of it like building code: overly strict linting rules don't always produce better code — they just frustrate developers into finding creative bypasses.

Key Takeaway: Effective password policies prioritize length and breach-checking over complexity requirements and forced expiration, balancing security with usability to prevent users from adopting worse practices as workarounds.