OWASP Passfault
is a free password policy replacement that will make passwords
stronger. It is not your conventional password strength meter. Even
with two-factor authentication, we can do better to improve the most
common “what you know” factor. Even low risk sites benefit. You can
try it here, or read about it here, or look at this presentation, or look at the code. I’ll summarize the presentation in the next few paragraphs.
Why don’t we just measure password strength? OWASP Passfault measures password strength using the following steps:
Why? Password Policies Stink.
Password policies are ineffective. They block some strong password patterns and they let some weak password patterns fly on by. Researchers at Carnegie Mellon did some studies on the effect of password policies on password strength. They state that “Successfully creating a password is significantly more difficult under stricter password policies”. They also found password length was the only significant predictor of eventual password strength. In summary: Password Policies Stink. They don’t work because they do not measure strength, but instead measure how well you comply with good advice. You can follow the advice and still make terrible passwords.Why don’t we just measure password strength? OWASP Passfault measures password strength using the following steps:
1. Identify Patterns
These are patterns that OWASP Passfault identifies currently:- Dictionary Patterns (currently English and Spainish)
- Words with mixed case
- Words with substituted special characters
- Words with inserted special characters
- Misspelled Words
- 133+ speak substitution
- Backwords words
- Keyboard Patterns (Currently US and Russian)
- Horizontal sequence of keys
- Diagonal sequence of keys
- Repeated keys
- Repeated Pattern
- Date Patterns
- Random set including international characters (currently latin and cyrillic)
1 comment:
In general I quite like the general thinking in this project, but the roadmap is concerning. Specifically, the development of the applet is concerning given that client side java is dead (no java plugin in mobile/tablet/metro browsers, and a whole heck of a lot of us that actively don't want java on client machines that do support it). Going with a straight script version would make a lot more sense, bypassing a plugin, but even for a plugin flash is a better option than java.
I would very much encourage the team to not spend cycles on the applet. Otherwise, a very promising project
Post a Comment