Difference between revisions of "Cheat Sheets"

Jump to: navigation, search
(Project Leader)
Line 29: Line 29:
Project Leaders:<br/>Jim Manico<br/>
Project Leaders:<br/>Jim Manico<br/>
Andrew Van Der Stock<br/>
Contributors: <br/>
Contributors: <br/>
Stephen de Vries<br/>
Michael Coates<br/>
Jim Bird
Jeff Williams<br/>
Dave Wichers<br/>
Kevin Wall<br/>
Jeffrey Walton<br/>
Eric Sheridan<br/>
Kevin Kenan<br/>
David Rook<br/>
Fred Donovan<br/>
Abraham Kang<br/>
.. and many more!
== Related Projects ==
== Related Projects ==

Revision as of 03:15, 5 February 2014

OWASP Project Header.jpg

OWASP Cheat Sheet Series

The OWASP Cheat Sheet Series was created to provide a concise collection of high value information on specific web application security topics. These cheat sheets were created by multiple application security experts and provide excellent security guidance in an easy to read format.

OWASP Cheat Sheets Project Homepage


The OWASP Proactive Controls document is free to use under the Creative Commons ShareAlike 3 License.

What is this?

The OWASP Proactive Controls

  • This document was written by developers for developers, to assist those new to secure development.

Email List

Project Email List

Project Leader

Project Leaders:
Jim Manico

Michael Coates
Jeff Williams
Dave Wichers
Kevin Wall
Jeffrey Walton
Eric Sheridan
Kevin Kenan
David Rook
Fred Donovan
Abraham Kang
.. and many more!

Related Projects

News and Events

  • [Feb 4 2014] New Wiki Template!


Owasp-incubator-trans-85.png Owasp-builders-small.png
Project Type Files DOC.jpg
What does this OWASP project offer you?
What releases are available for this project?
what is this project?
Name: OWASP Cheat Sheets Project (home page)
Purpose: This project was created to provide a concise collection of high value information on specific application security topics. These cheat sheets were created by multiple application security experts and provide excellent security guidance in an easy to read format.
License: Creative Commons Attribution ShareAlike 3.0 license
who is working on this project?
Project Leader(s):
Project Contributor(s):
  • Michael Coates
  • Eric Sheridan
  • Dave Wichers
  • Jeff Williams
  • Kevin Keenan
  • Abraham Kang
  • Dave Ferguson
  • Shreeraj Shah
  • Raul Siles
  • Colin Watson
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
Not Yet Published
last reviewed release
Not Yet Reviewed

other releases


Ensure all entities go through an appropriate and adequate form of authentication. All the application non-public resource must be protected and shouldn't be bypassed.

For more information, check Authentication Cheat Sheet

Session Management

Use secure session management practices that ensure that users authenticated users have a robust and cryptographically secure association with their session.

For more information, check Session Management Cheat Sheet

Access Control

Ensure that a user has access only to the resources they are entitled to. Perform access control checks on the server side on every request. All user-controlled parameters should be validated for entitlemens checks. Check if user name or role name is passed through the URL or through hidden variables. Prepare a ACL containing the Role-to-Function mapping and validate if the users are granted access as per the ACL.

For more information, check Access Control Cheat Sheet

Input Validation

Input validation is performed to minimize malformed data from entering the system. Input Validation is NOT the primary method of preventing XSS, SQL Injection. These are covered in output encoding below.

For more information, check Input Validation Cheat Sheet

Output Encoding

Output encoding is the primary method of preventing XSS and injection attacks. Input validation helps minimize the introduction of malformed data, but it is a secondary control.

For more information, check XSS (Cross Site Scripting) Prevention Cheat Sheet.

Cross Domain

Ensure that adequate controls are present to prevent against Cross-site Request Forgery, Clickjacking and other 3rd Party Malicious scripts.

For more information, check Cross Site Request Forgery

Secure Transmission

Ensure that all the applications pages are served over cryptographically secure HTTPs protocols. Prohibit the transmission of session cookies over HTTP.

For more information, check Transport Protection Cheat Sheet


Ensure that all the security related events are logged. Events include: User log-in (success/fail); view; update; create, delete, file upload/download, attempt to access through URL, URL tampering. Audit logs should be immutable and write only and must be protected from unauthorized access.

For more information, check Logging Cheat Sheet


Ensure that the size, type, contents and name of the uploaded files are validated. Uploaded files must not be accessible to users by direct browsing. Preferably store all the uploaded files in a different file server/drive on the server. All files must be virus scanned using a regularly updated scanner.