This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Testing for Weak password policy (OTG-AUTHN-007)

Revision as of 16:34, 6 March 2014 by Davide Danelon (talk | contribs)

Jump to: navigation, search
This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: Back to the OWASP Testing Guide Project:


The most prevalent and most easily administered authentication mechanism is the humble password. The password represents the keys to the kingdom, but is often subverted by users in the name of usability. In each of the recent high profile hacks that have revealed user credentials, it is lamented that most common passwords are still: 123456, password and qwerty.

Test objectives

Determine the resistance of the application's to brute force password guessing using available password dictionaries by evaluating the length, complexity, reuse and aging requirements of passwords.

How to test

  1. What characters are permitted and forbidden for use within a password?
  2. How often can a user change their password?
  3. When must a user change their password? After 90 days? After account lockout due to excessive logon attempts?
  4. How often can a user reuse a password? Does the application store the user's previous 8 passwords?
  5. How different must the next password be from the last password (or however many are stored by the application)?




See the OWASP article on Brute Force Attacks.


To mitigate the risk of easily guessed passwords facilitating unauthorised access there are two solutions: introduce additional authentication controls or introduce a password policy. The simplest and cheapest of these is the introduction of a password policy that ensures password length, complexity, reuse and aging.