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

Difference between revisions of "Authentication Cheat Sheet"

From OWASP
Jump to: navigation, search
(Implement Proper Password Strength Policy)
Line 12: Line 12:
 
= Authentication General Guidelines =
 
= Authentication General Guidelines =
 
   
 
   
== Implement Proper Password Strength Policy  ==
+
== Implement Proper Password Strength Controls ==
  
 
A key concern when using passwords for authentication is password strength. A "strong" password policy makes it difficult or even improbable for one to guess the password either by using manual or automated means. The following characteristics define strong a strong password:  
 
A key concern when using passwords for authentication is password strength. A "strong" password policy makes it difficult or even improbable for one to guess the password either by using manual or automated means. The following characteristics define strong a strong password:  
Line 24: Line 24:
 
'''Important applications''': Minimum of 6 characters in length.  
 
'''Important applications''': Minimum of 6 characters in length.  
  
'''Critical applications''': Minimum of 8 characters in length. (consider 2 factor authentication)  
+
'''Critical applications''': Minimum of 8 characters in length. (consider multi-factor authentication)  
  
'''Highly critical applications''': Consider 2 factor authentication  
+
'''Highly critical applications''': Consider multi-factor authentication  
  
 
<br>  
 
<br>  

Revision as of 21:07, 8 February 2010

Introduction

Authentication is the process of verification that an individual or an entity is who it claims to be. Authentication is commonly performed by submitting a user name or ID and one or more items of private information that only a given user should know.

Session Management is a process by which a server maintains the state of an entity interacting with it. This is required for a server to remember how to react to subsiquent requests throughout a transaction. Sessions are maintained on the server by a session identifier which can be passed back and forward between the client and server when mtransmitting and receiving requests. Sessions should be unique per user and computationally very difficult to predict.

For more information on Authentication, please see the OWASP Guide_to_Authentication page.

Authentication General Guidelines

Implement Proper Password Strength Controls

A key concern when using passwords for authentication is password strength. A "strong" password policy makes it difficult or even improbable for one to guess the password either by using manual or automated means. The following characteristics define strong a strong password:

1.Password Length

The longer the password the more combinations possible combinations of characters exist and is hence more difficult to guess.


Important applications: Minimum of 6 characters in length.

Critical applications: Minimum of 8 characters in length. (consider multi-factor authentication)

Highly critical applications: Consider multi-factor authentication


2. Password complexity


Implement Secure Password Recovery Mechanism

Utilize Multi-Factor Authentication

Transmit Passwords Only Over TLS

Implement Account Lockout

Session Management General Guidelines

Transmit Session ID's Only Over TLS

Ensure Session ID's are Cryptographically Strong and Random

Implement Idle And Absolute Timeout

Caching & Privacy

Cookie Security

OWASP Cheat Sheets Project Homepage


References

Authors and Primary Editors

Eoin Keary eoinkeary[at]owasp.org