Difference between revisions of "OWASP Cheat Sheet Series"

From OWASP
Jump to: navigation, search
m (Add update of the Password Storage CS)
m (News and Events)
 
(56 intermediate revisions by 3 users not shown)
Line 6: Line 6:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
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 various application security professionals who have expertise in specific topics. We hope that the OWASP Cheat Sheet Series provides you with excellent security guidance in an easy to read format.
+
== Our goal ==
  
If you have any questions about the OWASP Cheat Sheet Series, please email the project leader [mailto:jim.manico@owasp.org Jim Manico] or subscribe to our [https://lists.owasp.org/mailman/listinfo/owasp-cheat-sheets project email list].
+
The OWASP Cheat Sheet Series was created to provide a concise collection of high value information on specific application security topics. These cheat sheets were created by various application security professionals who have expertise in specific topics. We hope that the OWASP Cheat Sheet Series provides you with excellent security guidance in an easy to read format.
  
== Authors ==
+
If you have any questions about the OWASP Cheat Sheet Series, please email the project leaders [mailto:jim.manico@owasp.org Jim Manico] or [mailto:dominique.righetto@owasp.org Dominique Righetto], contact us on the project's Slack channel or on our [https://lists.owasp.org/mailman/listinfo/owasp-cheat-sheets project email list] (Slack is highly preferred over the email list).
  
Project Leaders: [https://www.owasp.org/index.php/User:Jmanico Jim Manico] and  [https://www.owasp.org/index.php/User:Dominique_RIGHETTO Dominique Righetto] [mailto:dominique.righetto@owasp.org @]
+
== Migration to GitHub ==
Contributors: Paweł Krawczyk, Mishra Dhiraj, Shruti Kulkarni, Torsten Gigler, Michael Coates, Jeff Williams, Dave Wichers, Kevin Wall, Jeffrey Walton, Eric Sheridan, Kevin Kenan, David Rook, Fred Donovan, Abraham Kang, Dave Ferguson, Shreeraj Shah, Raul Siles, Colin Watson, Neil Matatall, Zaur Molotnikov and <b>many more</b>!
 
  
== OWASP Cheat Sheets ==
+
Project has been fully migrated to [https://github.com/OWASP/CheatSheetSeries GitHub].
  
{{Cheatsheet_Navigation_Body}}
+
This page is used as the OWASP homepage of the project, all the project content is hosted on the [https://github.com/OWASP/CheatSheetSeries GitHub repository] and we work '''only from''' this repository, '''wiki is not used anymore'''.
  
| valign="top"  style="padding-left:25px;width:200px;" |
+
So, from now, only a GitHub account is needed to contribute :)
  
== Quick Access ==
+
== Bridge between the projects OWASP Proactive Controls/OWASP Application Security Verification Standard and OWASP Cheat Sheet Series ==
OWASP Cheatsheet Series Book : April 2015 [https://www.owasp.org/images/9/9a/OWASP_Cheatsheets_Book.pdf PDF download].
 
  
== Email List ==
+
A work channel has been created between these 2 projects and the Cheat Sheet Series using the following process (''OPC = OWASP Proactive Controls / OASVS = OWASP Application Security Verification Standard / OCS = OWASP Cheat Sheet''):
[https://lists.owasp.org/mailman/listinfo/owasp-cheat-sheets Project Email List]
 
  
== Licensing ==
+
* When a Cheat Sheet is missing for a point in OPC/OASVS then the OCS will handle the missing and create one. When the Cheat Sheet is ready then the reference is added by OPC/OASVS.
The OWASP <i>Cheat Sheet Series</i> is free to use under the [https://creativecommons.org/licenses/by-sa/3.0/us/ Creative Commons ShareAlike 3 License].
+
* If a Cheat Sheet exists for an OPC/OASVS point but the content do not provide the expected help then the Cheat Sheet is updated to provide the content needed/expected.
  
== Related Projects ==
+
The reason of the creation of this bridge is to help the OCS/OASVS projects by providing them:
* [[OWASP Proactive Controls]]
 
* [https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP Application Security Verification Standard Project]
 
  
== News and Events ==
+
* A consistent source for the requests regarding new Cheat Sheets.
* [Feb 18 2018] [[Password_Storage_Cheat_Sheet|Password Storage Cheat Sheet]] updated
+
* Same approach about the update of the existing Cheat Sheets.
* [Jan 14 2018] [[Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet|Insecure Direct Object Reference Prevention Cheat Sheet]] updated
+
* A usage context for the Cheat Sheet and a quick source of feedack about the quality and the efficiency of the Cheat Sheet.
* [Dec 04 2017] [[Ruby_on_Rails_Cheatsheet|Ruby On Rails Cheat Sheet]] updated
 
* [Nov 19 2017] [[JSON_Web_Token_(JWT)_Cheat_Sheet_for_Java|JWT Cheat Sheet for Java]] updated
 
* [Nov 17 2017] [[OS_Command_Injection_Defense_Cheat_Sheet|OS Command Injection Defense Cheat Sheet]] added to project
 
* [Nov 04 2017] [[Authorization_Testing_Automation|Authorization Testing Automation Cheat Sheet]] added to project
 
* [Jan 17 2017] [[XML_Security_Cheat_Sheet|XML Security Cheat Sheet]] added to project
 
* [Feb 06 2016] New navigation template rolled out project-wide
 
* [Jun 11 2015] [[SAML_Security_Cheat_Sheet|SAML Cheat Sheet]] added to project
 
* [Feb 11 2015] [https://www.owasp.org/images/9/9a/OWASP_Cheatsheets_Book.pdf Cheat Sheet "book"] added to project
 
* [Apr 04 2014] All non-draft cheat sheets moved to new wiki template!
 
* [Feb 04 2014] Project-wide cleanup started
 
  
==Classifications==
+
It is not mandatory that a request for a new Cheat Sheet (or for an update) come only from OPC/OASVS, it is just a extra channel.
  
  {| width="200" cellpadding="2"
+
<pre>Requests from OPC/OASVS are flagged with a special label in the GitHub repository issues list in order to identify them and set them as a top level priority.</pre>
  |-
 
  | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-labs-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Labs_Projects]]
 
  | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] 
 
  |-
 
  | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
 
  |-
 
  | colspan="2" align="center"  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 
  |-
 
  | colspan="2" align="center"  | [[File:Project_Type_Files_DOC.jpg|link=]]
 
  |}
 
  
|}
+
== Project Leaders ==
  
= Master Cheat Sheet =
+
* [https://www.owasp.org/index.php/User:Jmanico Jim Manico] [mailto:jim.manico@owasp.org @]
 +
* [https://www.owasp.org/index.php/User:Dominique_RIGHETTO Dominique Righetto] [mailto:dominique.righetto@owasp.org @]
  
==Authentication==
+
== Contributors of the V1 of the project ==  
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 [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]
+
Paweł Krawczyk, Mishra Dhiraj, Shruti Kulkarni, Torsten Gigler, Michael Coates, Jeff Williams, Dave Wichers, Kevin Wall, Jeffrey Walton, Eric Sheridan, Kevin Kenan, David Rook, Fred Donovan, Abraham Kang, Dave Ferguson, Shreeraj Shah, Raul Siles, Colin Watson, Neil Matatall, Zaur Molotnikov, Manideep Konakandla, Santhosh Tuppad and '''many more'''!
  
==Session Management==
+
== Contributors of the V2 of the project ==  
  
Use secure session management practices that ensure that authenticated users have a robust and cryptographically secure association with their session.  
+
See [https://github.com/OWASP/CheatSheetSeries/graphs/contributors here] for a complete list.
  
For more information, check [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet Session Management Cheat Sheet]
+
| valign="top"  style="padding-left:25px;width:200px;" |
  
==Access Control==
+
== GitHub repository ==
  
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 an ACL containing the Role-to-Function mapping and validate if the users are granted access as per the ACL.
+
Repository is [https://github.com/OWASP/CheatSheetSeries here].
  
For more information, check [https://www.owasp.org/index.php/Access_Control_Cheat_Sheet Access Control Cheat Sheet]
+
== Offline Cheat Sheets collection ==
  
==Input Validation==
+
A offline website of all Cheat Sheets can be obtained [https://github.com/OWASP/CheatSheetSeries#offline-website here].
  
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.
+
== Slack & Twitter ==
  
For more information, check [https://www.owasp.org/index.php/Input_Validation_Cheat_Sheet Input Validation Cheat Sheet]
+
Slack channel information:
 +
* Server <code>owasp.slack.com</code>
 +
* Channel <code>cheatsheets</code>
  
==Output Encoding==
+
Twitter hash tag: '''#[https://twitter.com/search?q=%23owaspcheatsheetseries&src=typd owaspcheatsheetseries]'''
  
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.
+
== Email List ==
  
For more information, check [https://www.owasp.org/index.php/XSS_Prevention_Cheat_Sheet XSS (Cross Site Scripting) Prevention Cheat Sheet].
+
[https://lists.owasp.org/mailman/listinfo/owasp-cheat-sheets Project Email List]
  
==Cross Domain==
+
Still used for technical discussion '''but we highly prefer''':
 +
* The Slack channel for announcement and technical discussion.
 +
* The Twitter hash tag for announcement only.
  
Ensure that adequate controls are present to prevent against Cross-site Request Forgery, Clickjacking and other 3rd Party Malicious scripts.
+
== Project classifications ==
  
For more information, check [https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet Cross Site Request Forgery]
+
  {| width="200" cellpadding="2"
 +
  |-
 +
  | rowspan="3" align="center" valign="top" width="50%" | [[File:Midlevel_projects.png|130px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects|Lab Project]]
 +
  | align="center" valign="top" width="50%" | [[File:Owasp-builders-small.png|link=Builders]] 
 +
  |-
 +
  | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=Defenders]]
 +
  |-
 +
  | align="center" valign="center" width="50%" |
 +
  |-
 +
  | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 +
  |-
 +
  | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
 +
  |}
  
==Secure Transmission==
+
== Licensing ==
  
Ensure that all the applications pages are served over cryptographically secure HTTPs protocols. Prohibit the transmission of session cookies over HTTP.
+
The OWASP <i>Cheat Sheet Series</i> is free to use under the [https://creativecommons.org/licenses/by-sa/3.0/us/ Creative Commons ShareAlike 3 License].
  
For more information, check [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Protection Cheat Sheet]
+
== Related Projects ==
  
==Logging==
+
* [[OWASP Proactive Controls]]
 +
* [https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP Application Security Verification Standard Project]
 +
 
 +
== News and Events ==
 +
* [Feb 23 2019] V2 released.
 +
* [Feb 22 2019] Migration to [https://github.com/OWASP/CheatSheetSeries GitHub] finished.
 +
* [Dec 28 2018] Start migration of the cheat sheets collection to [https://github.com/OWASP/CheatSheetSeries GitHub].
 +
* [Dec 01 2018] [[Injection_Prevention_Cheat_Sheet_in_Java|Injection Prevention Cheat Sheet in Java]] updated
 +
* [Nov 24 2018] [[Securing_Cascade_Style_Sheets_(CSS)_Cheat_Sheet|Securing Cascade Style Sheets Cheat Sheet]] added to project
 +
* [Nov 08 2018] Creation and sharing of the project logos
 +
* [Oct 13 2018] [[Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet|CSRF Prevention Cheat Sheet]] refactored
 +
* [Sep 25 2018] [[Abuse_Case_Cheat_Sheet|Abuse Case Cheat Sheet]] added to project
 +
* [Aug 25 2018] Cleanup of Cheat Sheets finished
 +
* [Jul 15 2018] [[Error_Handling_Cheat_Sheet|Error Handling Cheat Sheet]] added to project
 +
* [Jun 12 2018] Made available the PDF book of all Cheat Sheets
 +
* [May 10 2018] [[Protect_FileUpload_Against_Malicious_File|Protect File Upload Against Malicious File Cheat Sheet]] updated
 +
* [Mar 18 2018] [[Password_Storage_Cheat_Sheet|Password Storage Cheat Sheet]] updated
 +
* [Feb 21 2018] [[HTML5_Security_Cheat_Sheet|HTML5 Security Cheat Sheet]] updated
 +
* [Feb 18 2018] [[Password_Storage_Cheat_Sheet|Password Storage Cheat Sheet]] updated
 +
* [Jan 14 2018] [[Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet|Insecure Direct Object Reference Prevention Cheat Sheet]] updated
 +
* [Dec 04 2017] [[Ruby_on_Rails_Cheatsheet|Ruby On Rails Cheat Sheet]] updated
 +
* [Nov 19 2017] [[JSON_Web_Token_(JWT)_Cheat_Sheet_for_Java|JWT Cheat Sheet for Java]] updated
 +
* [Nov 17 2017] [[OS_Command_Injection_Defense_Cheat_Sheet|OS Command Injection Defense Cheat Sheet]] added to project
 +
* [Nov 04 2017] [[Authorization_Testing_Automation|Authorization Testing Automation Cheat Sheet]] added to project
 +
* [Jan 17 2017] [[XML_Security_Cheat_Sheet|XML Security Cheat Sheet]] added to project
 +
* [Feb 06 2016] New navigation template rolled out project-wide
 +
* [Jun 11 2015] [[SAML_Security_Cheat_Sheet|SAML Cheat Sheet]] added to project
 +
* [Feb 11 2015] [https://www.owasp.org/images/9/9a/OWASP_Cheatsheets_Book.pdf Cheat Sheet "book"] added to project
 +
* [Apr 04 2014] All non-draft cheat sheets moved to new wiki template!
 +
* [Feb 04 2014] Project-wide cleanup started
  
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 [https://www.owasp.org/index.php/Logging_Cheat_Sheet Logging Cheat Sheet]
+
|}
  
==Uploads==
+
= Roadmap =
  
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.
+
Roadmap is managed using the [https://github.com/OWASP/CheatSheetSeries/projects/1 GitHub feature] of the repository.
  
= Roadmap =
+
= Project Logo =
  
'''Global:'''
+
'''Project is now finished, we let the specification online for further evolution of the logo.'''
  
* Bring all cheat sheets out of draft.
+
Big thanks to Amélie Didion for the design work.
* Go through the cheat sheets to make sure what they recommend is consistent with ASVS.
 
* Move all code snippets of CS from '''pre''' tag to '''syntaxhighlight''' tag to enhance CS readability.
 
* Find a way to automate the generation of a PDF referential file gathering all CS.
 
* Go through the cheat sheets to make sure they follow the CS guideline.
 
* Create a Slack or Discord exchange area for the community.
 
* Create branding stickers for the project.
 
  
 +
== Logo files ==
  
'''Next work on Cheat Sheets (CS) and work assignment:'''
+
Logo files are hosted on the official OWASP dedicated [https://github.com/OWASP/owasp-swag/tree/master/projects/cheat-sheet-series Github repository].
  
* Server Side Request Forgery Defense CS:
+
Logo n°1:
** '''Action:''' Create it.
 
** '''People in charge:''' Dominique Righetto.
 
** '''Status:''' In backlog.
 
* [[Forgot_Password_Cheat_Sheet|Forgot Password]] CS:
 
** '''Action:''' Add a POC in order to provide actionable code.
 
** '''People in charge:''' Dominique Righetto.
 
** '''Status:''' In backlog.
 
* [[Password_Storage_Cheat_Sheet|Password Storage]] CS:
 
** '''Action:''' Add a POC in order to provide actionable code about Argon2 usage.
 
** '''People in charge:''' Dominique Righetto.
 
** '''Status:''' <span style="background:#008000;color:#ffffff">Work in progress</span>.
 
* [[OS_Command_Injection_Defense_Cheat_Sheet|OS Command Injection Defense]] CS:
 
** '''Action:''' Add information about system command escaping.
 
** '''People in charge:''' Dominique Righetto.
 
** '''Status:''' In backlog.
 
* [[Ruby_on_Rails_Cheatsheet|Ruby On Rails]] CS:
 
** '''Action:''' CS complete refactoring.
 
** '''People in charge:''' Zaur Molotnikov.
 
** '''Status:''' <span style="background:#008000;color:#ffffff">Work in progress</span>.
 
  
 +
[https://github.com/OWASP/owasp-swag/blob/master/projects/cheat-sheet-series/owasp-1.png]
  
= Cheat sheet Guideline =
+
Logo n°2:
  
== Cheat sheet content ==
+
[https://github.com/OWASP/owasp-swag/blob/master/projects/cheat-sheet-series/owasp-2.png]
  
The key points that all cheat sheets (called '''CS''') must provides are the following:
+
== Objective ==
  
# Address a single topic (ex: password storage, OS command injection, REST service, CSRF, HTML5 new features security...).
+
This section contains the information that we have gathered and plan to use for the creation of the project logo and related design materials.
# Be concise and focused: A cheat sheet must be directly actionable (a CS is not a guide) and must be directly useful for a developer.
 
# Do not re-address topic handled by others CS. In this case, the target CS will be enhanced with missing points.
 
# When applicable, provide a solution proposal implementation through a full documented POC on a public well know Git repository (GitHub is highly prefered), the POC can be used as a '''playground''' for a developer wanting to play/evaluate your solution proposal.
 
  
== Cheat sheet structure ==
+
The first phase of the work is to commission a project logo.
  
A CS must have these sections:
+
== Phase 1: Logo ==
  
# '''Introduction''': Provide high level information about the topic in order to introduce it to people that do not know it. You can add pointer to external sources if needed but at least give an overview allowing a reader to continue on the CS. You can also add schema or diagram in any part of the CS but be sure to respect the copyright of the source file.
+
=== Introduction ===
# '''Context''': Describe the security issues that are bring or commonly meet when someone must work on this topic.
 
# '''Objective''': Describe the objective of the CS. What the CS will bring to the reader?
 
# '''Proposition''':
 
## Describe how to address the security issues in a possible technology agnostic approach.
 
## Using your POC, describe your solution proposal in the more teaching possible way.
 
# '''Sources of the prototype''': Add pointer to the public GitHub repository on which the source code of POC is hosted.
 
  
 +
The project requires a logo which will comprise three components:
  
For the code snippet, use the mediawiki tag '''syntaxhighlight''':
+
* Graphical element indicating the idea or use of the cheat sheets
* Tag [https://www.mediawiki.org/wiki/Extension:SyntaxHighlight documentation].
+
* The project title
* Supported [http://pygments.org/languages languages].
+
* Motto/straplines.
  
 +
Not all of these will necessarily be shown together at the same time. Phase 1 requires the creation of a logo, which may be used with one, two or all three of these components.
  
If you want to be careful in order to prevent to break something in the target existing CS, you can follow this contribution procedure:
+
The logo will be used in many ways such as on a website banner, or just the graphical element on a bag, or the graphical element and a motto/strapline on a t-shirt. These other outputs are not included in the scope of Phase 1.
# Take a copy of the CS that you want to enhance (mediawiki syntax in the source tab).
 
# Add your enhancement and publish the updated CS on the same GitHub repository than your POC (it support the mediawiki syntax).
 
# Notify the CS Community using this mailing [https://lists.owasp.org/mailman/listinfo/owasp-cheat-sheets list] and the CS Community will review the CS using GitHub comments system.
 
# When the feedback loop is finished, the CS Community will help you to have right access to the wiki in order to update the CS.
 
  
== Cheat sheet template ==
+
=== Project Name ===
  
If the target CS is a new one then please use the following template struture.  
+
The project name is ''OWASP Cheat Sheet Series project''. The project name will be positioned next to the graphical element in some outputs, and this layout must be provided. In other cases, the project name will not be included beside the logo.
  
It allow you to work:
+
=== Motto/Strapline ===
* Online by using the wiki ''Show preview'' option.
 
* Offline by using an text editor like [https://atom.io/ Atom] with the [https://atom.io/packages/language-mediawiki mediawiki plugin].
 
  
<syntaxhighlight lang="html" highlight="10,18,24,31,38,44">
+
Three mottos/straplines will be used in the logo - they are context dependent:
__NOTOC__
 
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div>
 
  
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
+
* ''Life is too short, AppSec is tough, Cheat!''
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
+
* ''Its not cheating if you do it for the right reasons''
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
+
* ''Sometimes the only good thing to do is cheat''.
  
__TOC__{{TOC hidden}}
+
The logo layout must allow for any of these or none to be included.
  
= Introduction =
+
=== Layout, Media Formats and Colours ===
  
<pre>
+
Some media or placements may mean the motto/strapline does not fit or is not needed. Therefore the logo must be usable with, or without, the motto/strapline.
Provide high level information about the topic in order to introduce it to people that do not know it.
 
You can add pointer to external sources if needed but at least give an overview allowing a reader to continue on the CS.
 
You can also add schema or diagram in any part of the CS but be sure to respect the copyright of the source file.
 
</pre>
 
  
= Context =
+
The logo will need to be used at multiple scales. For example, if the logo is square excluding the motto/strapline, the following formats must work
  
<pre>
+
* Low-resolution use on web pages (e.g. as small as 100x100 pixels excluding moto/strapline)
Describe the security issues that are bring or commonly meet when someone must work on this topic.
+
* Medium resolution use on fabric such as t-sirts or bags (e.g. 900x900 pixels at 150 dpi)
</pre>
+
* High-resolution use on large posters and banners (e.g. as large as 5,000x5,000 pixels at 300dpi).
  
= Objective =
+
The logo may be printed in CMYK for physical media, but must also have RGB colours for screen use. Additionally the logo must also be available in grayscale, and separately as single colour (i.e. black and white without any tones).
  
<pre>
+
=== Deliverables Required ===
Describe the objective of the CS.
 
What the CS will bring to the reader.
 
</pre>
 
  
= Proposition =
+
All outputs must be provided digitally:
  
<pre>
+
# Logo demonstrating how it looks with just the graphical element, the graphical element with the project title, and the graphical element with each of the mottos/straplines, and everything together
1. Describe how to address the security issues in a possible technology agnostic approach.
+
# Source layered vector graphic files created in Adobe Illustrator
2. Using your POC, describe your solution proposal in the more teaching possible way. Use "syntaxhighlight" tag for code snippet.
+
# Exported versions for quick use low, medium and high resolution full-colour PNG/JPEGs in RGB and CMYK
</pre>
+
# Colour and font specification.
  
= Sources of the prototype =
+
Rights/licensing:
  
<pre>
+
# The designer will not retain any rights - all design and use rights will be given to OWASP, who will publish the logo and files using am open source licence, and OWASP will be able to use the logo, source files, ideas, designs in any manner it desires in any media in any quantity, without any additional payments, commission or royalties to the designer or anyone else
Add pointer to the public GitHub repository on which the source code of POC is hosted.
+
# All fonts used in the design must be provided to OWASP and comply with the above requirements
</pre>
 
  
= Authors and Primary Editors =
 
  
<pre>
 
Add your name and email.
 
</pre>
 
  
= Other Cheatsheets =
+
== Future Phases: Other Graphical Elements ==
  
{{Cheatsheet_Navigation_Body}}
+
Scope TBC - Banners, t-shirts, etc
  
|}
+
Background pictures (picture provider and designer will be cited on the project site):
 +
* ''A smart tech looking woman reading a piece of paper (the cheatsheet) while resting on a beach.''
 +
* ''A woman hand holding cards with an ace up the sleeve.''
  
[[Category:Cheatsheets]]
+
Pictures proposal (just a proposal as bootstrap, others pictures can be used):
</syntaxhighlight>
+
* Cards:
 +
** https://www.pexels.com/photo/woman-holding-queen-of-hearts-and-diamonds-922706/
 +
** https://www.pexels.com/photo/ace-card-gambling-hand-274373/
 +
** https://www.pexels.com/photo/ace-bet-business-card-262333/
 +
* Beach:
 +
** https://www.pexels.com/photo/laptop-mockup-notebook-outside-4778/
 +
** https://www.pexels.com/photo/apple-check-computer-female-7079/
 +
** https://www.pexels.com/photo/beach-beach-chair-blur-casual-319921/
 +
** https://www.pexels.com/photo/close-up-of-woman-typing-on-keyboard-of-laptop-6352/
 +
** https://www.pexels.com/photo/black-and-gray-computer-laptop-159784/
  
  

Latest revision as of 01:58, 23 February 2019

Lab big.jpg
Cheatsheets-header.jpg

Our goal

The OWASP Cheat Sheet Series was created to provide a concise collection of high value information on specific application security topics. These cheat sheets were created by various application security professionals who have expertise in specific topics. We hope that the OWASP Cheat Sheet Series provides you with excellent security guidance in an easy to read format.

If you have any questions about the OWASP Cheat Sheet Series, please email the project leaders Jim Manico or Dominique Righetto, contact us on the project's Slack channel or on our project email list (Slack is highly preferred over the email list).

Migration to GitHub

Project has been fully migrated to GitHub.

This page is used as the OWASP homepage of the project, all the project content is hosted on the GitHub repository and we work only from this repository, wiki is not used anymore.

So, from now, only a GitHub account is needed to contribute :)

Bridge between the projects OWASP Proactive Controls/OWASP Application Security Verification Standard and OWASP Cheat Sheet Series

A work channel has been created between these 2 projects and the Cheat Sheet Series using the following process (OPC = OWASP Proactive Controls / OASVS = OWASP Application Security Verification Standard / OCS = OWASP Cheat Sheet):

  • When a Cheat Sheet is missing for a point in OPC/OASVS then the OCS will handle the missing and create one. When the Cheat Sheet is ready then the reference is added by OPC/OASVS.
  • If a Cheat Sheet exists for an OPC/OASVS point but the content do not provide the expected help then the Cheat Sheet is updated to provide the content needed/expected.

The reason of the creation of this bridge is to help the OCS/OASVS projects by providing them:

  • A consistent source for the requests regarding new Cheat Sheets.
  • Same approach about the update of the existing Cheat Sheets.
  • A usage context for the Cheat Sheet and a quick source of feedack about the quality and the efficiency of the Cheat Sheet.

It is not mandatory that a request for a new Cheat Sheet (or for an update) come only from OPC/OASVS, it is just a extra channel.

Requests from OPC/OASVS are flagged with a special label in the GitHub repository issues list in order to identify them and set them as a top level priority.

Project Leaders

Contributors of the V1 of the project

Paweł Krawczyk, Mishra Dhiraj, Shruti Kulkarni, Torsten Gigler, Michael Coates, Jeff Williams, Dave Wichers, Kevin Wall, Jeffrey Walton, Eric Sheridan, Kevin Kenan, David Rook, Fred Donovan, Abraham Kang, Dave Ferguson, Shreeraj Shah, Raul Siles, Colin Watson, Neil Matatall, Zaur Molotnikov, Manideep Konakandla, Santhosh Tuppad and many more!

Contributors of the V2 of the project

See here for a complete list.

GitHub repository

Repository is here.

Offline Cheat Sheets collection

A offline website of all Cheat Sheets can be obtained here.

Slack & Twitter

Slack channel information:

  • Server owasp.slack.com
  • Channel cheatsheets

Twitter hash tag: #owaspcheatsheetseries

Email List

Project Email List

Still used for technical discussion but we highly prefer:

  • The Slack channel for announcement and technical discussion.
  • The Twitter hash tag for announcement only.

Project classifications

Lab Project Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

Licensing

The OWASP Cheat Sheet Series is free to use under the Creative Commons ShareAlike 3 License.

Related Projects

News and Events


Roadmap is managed using the GitHub feature of the repository.