OWASP Guide Project

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP Developer Guide
The OWASP Developer Guide 2014 is a dramatic re-write of one of OWASP's first and most downloaded projects. The focus moves from countermeasures and weaknesses to secure software engineering.

Introduction
The OWASP Developer Guide is the original OWASP project. It was first published in 2002, when Ajax was only a mote in Microsoft's eye with the new e-mail notification in Outlook Web Access (and only if you used Internet Explorer). Since then, the web has come a long way. Unfortunately, the Developer Guide never really took off with the intended audience: developers. The original Guide was more a how to perform a web application penetration test, material now better covered in the OWASP Testing Guide.

The Developer Guide 2014 is a "first principles" book - it's not specific to any one language or framework, as they all borrow ideas and syntax from each other. There are highly specific issues in different languages, such as PHP configuration settings or Spring MVC issues, but we need to look past these differences and apply the basic tenets of secure system engineering to application security.

The major themes in the Developer Guide include:


 * Foundation
 * Architecture
 * Design
 * Build
 * Configure
 * Operate

We are re-factoring the original material from the Developer Guide 2.0, released in July 2005, and bring it into the modern world, and focus it tightly on modern web apps that use Ajax and RESTful API, and of course, mobile applications. All testing material will move to the OWASP Testing Guide and all code review material to the OWASP Code Review Guide.

Intended audience
The primary audience for the new version of the Developer Guide is Architects and Developers. The Developer Guide can still be used by penetration testers who want to move up to software verification or improve their craft, but the primary focus will become how to implement secure software from first principles.


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

Presentation

 * TBA

Project Leader

 * Brad Chesney Brad Chesney bradchesney79@gmail.com
 * Steven van der Baan steven.van.der.baan@owasp.org

Related Projects

 * OWASP Application Security Verification Standard
 * OWASP Code Review Guide
 * OWASP Testing Guide

Ohloh

 * https://www.ohloh.net/p/DevGuide

Licensing
OWASP Developer Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download
We are developing the Guide in the open on GitHub.


 * OWASP Developer Guide on GitHub

All versions of the Developer Guide are also there for historical purposes.

Please come join us there and help write the next edition!

News and Events

 * [1 Feb 2014] New OWASP document template installed

In Print
Version 2.0.1 can be purchased for historical research on Lulu.com:


 * OWASP Developer Guide

Classifications

 * }

=FAQs=


 * When will the new version be released?
 * Hard to say. We all have day jobs and do this as an altruistic endeavor to make the world a better place. Making progress as fast as we can...


 * I only have a few minutes per month to help! How do I get involved?
 * Please join the mail list, introduce yourself, go find something that needs fixing in the GitHub issue list. Not familiar with git? Get the Dev Guide on GitHub and make edits on your machine, email me your work and I will commit it to the project (blaming you in the commit message via a parseable format that I can extract for attribution).


 * I really want to help big time. How do I get involved?
 * Please join the mail list, introduce yourself, go find something that needs writing or missing on GitHub, write the first draft and mail it to us on the mail list. We'll take it from there!


 * How do I get commit privileges on GitHub?
 * Fork the Dev Guide on GitHub, write something for the Guide, and send a pull request. Rinse and repeat! :) Provide a few quality pull requests and we may give in and let you have at it directly.

= Acknowledgements =

Volunteers
The OWASP Developer Guide is developed by a worldwide team of volunteers. The primary contributors to date have been:

Editors

 * Brad Chesney
 * Steven Van Der Baan
 * Andrew van der Stock
 * Abraham Kang

Project manager

 * Matt Konda

Authors

 * Tom Chen

Reviewers

 * TBA

OWASP Guide 2.0
The OWASP Developer Guide 2.0 would not be where it is today without the generous gift of volunteer time and effort from many individuals. If you are one of them, and not on this list, please contact Brad or Steven.


 * Abraham Kang
 * Adrian Wiesmann
 * Alex Russell
 * Amit Klein
 * Andrew van der Stock
 * Brian Greidanus
 * Christopher Todd
 * Darrel Grundy
 * David Endler
 * Denis Pilipchuk
 * Dennis Groves
 * Derek Browne
 * Eoin Keary
 * Ernesto Arroyo
 * Frank Lemmon
 * Gene McKenna
 * Hal Lockhart
 * Izhar By-Gad
 * Jeremy Poteet
 * José Pedro Arroyo
 * K.K. Mookhey
 * Kevin McLaughlin
 * Mark Curphey
 * Martin Eizner
 * Mikael Simonsson
 * Neal Krawetz
 * Nigel Tranter
 * Raoul Endres
 * Ray Stirbei
 * Richard Parke
 * Robert Hansen
 * Roy McNamara
 * Steve Taylor
 * Sverre Huseby
 * Tim Smith
 * William Hau

If you helped and you're not here, please e-mail us at the mail list, and this list will be fixed up.
= Road Map and Getting Involved =

2015 Planning

 * Working out strengths & responsibilities

Getting involved
Involvement in the development and promotion of Developer Guide is actively encouraged!

You do not have to be a security expert in order to contribute.

Some of the ways you can help:
 * Technical editing
 * Review
 * Diagrams
 * Graphic design
 * Code snippets in your favorite language

See more detailed instructions on the FAQ page.

=Project About=