OWASP Cheat Sheet Series
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 Dominique Righetto or Jim Manico, contact us on the project's Slack channel or on our Google Group (Slack is highly preferred over the Google Group).
The archives of the old mailing list can be consulted here.
The official website on which all the cheat sheets are hosted is https://cheatsheetseries.owasp.org .
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):
The reason of the creation of this bridge is to help the OCS/OASVS projects by providing them:
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.
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.
Website of the here.
Repository is here.
Offline Cheat Sheets collection
A offline website of all Cheat Sheets can be obtained here.
Slack & Twitter
Slack channel information:
Twitter hash tag: #owaspcheatsheetseries
Still used for technical discussion but we highly prefer:
The OWASP Cheat Sheet Series is free to use under the Creative Commons ShareAlike 3 License.
Roadmap is managed using the GitHub feature of the repository.
Project is now finished, we let the specification online for further evolution of the logo.
Big thanks to Amélie Didion for the design work.
Logo files are hosted on the official OWASP dedicated Github repository.
This section contains the information that we have gathered and plan to use for the creation of the project logo and related design materials.
The first phase of the work is to commission a project logo.
Phase 1: Logo
The project requires a logo which will comprise three components:
- Graphical element indicating the idea or use of the cheat sheets
- The project title
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.
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.
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.
Three mottos/straplines will be used in the logo - they are context dependent:
- Life is too short, AppSec is tough, Cheat!
- Its not cheating if you do it for the right reasons
- Sometimes the only good thing to do is cheat.
The logo layout must allow for any of these or none to be included.
Layout, Media Formats and Colours
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.
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
- Low-resolution use on web pages (e.g. as small as 100x100 pixels excluding moto/strapline)
- Medium resolution use on fabric such as t-sirts or bags (e.g. 900x900 pixels at 150 dpi)
- High-resolution use on large posters and banners (e.g. as large as 5,000x5,000 pixels at 300dpi).
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).
All outputs must be provided digitally:
- 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
- Source layered vector graphic files created in Adobe Illustrator
- Exported versions for quick use low, medium and high resolution full-colour PNG/JPEGs in RGB and CMYK
- Colour and font specification.
- 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
- All fonts used in the design must be provided to OWASP and comply with the above requirements
Future Phases: Other Graphical Elements
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.
Pictures proposal (just a proposal as bootstrap, others pictures can be used):