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 "OWASP Guide Project"

From OWASP
Jump to: navigation, search
m (Adding my email address)
 
(29 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
=Main=
 
=Main=
  
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+
<div style="width:100%;height:90px;border:0,margin:0;overflow: hidden;">[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]</div>
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
Line 39: Line 39:
 
== Project Leader ==
 
== Project Leader ==
  
* [[Special:vanderaj|Andrew van der Stock]] vanderaj@owasp.org
+
* [[User:Brad Chesney|Brad Chesney ]] Brad Chesney bradchesney79@gmail.com
 +
* [[User:Steven van der Baan|Steven van der Baan]] steven.van.der.baan@owasp.org
  
 
== Related Projects ==
 
== Related Projects ==
Line 46: Line 47:
 
* [[:Category:OWASP_Code_Review_Project|OWASP Code Review Guide]]
 
* [[:Category:OWASP_Code_Review_Project|OWASP Code Review Guide]]
 
* [[:Category:OWASP_Testing_Project|OWASP Testing Guide]]
 
* [[:Category:OWASP_Testing_Project|OWASP Testing Guide]]
 +
 +
== Ohloh ==
 +
 +
*https://www.ohloh.net/p/DevGuide
  
 
==Licensing==
 
==Licensing==
Line 90: Line 95:
  
 
; When will the new version be released?
 
; When will the new version be released?
: We are hoping to have the first milestone, consisting of the Authentication, Session Management, Access Control, Input validation and output encoding, and Data Protection chapters complete by September 2014. If we get more volunteers, sooner.
+
: 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?
 
; 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 and then fix it and mail it back to us. We'll take it from there!
+
: Please join the [https://lists.owasp.org/mailman/listinfo/owasp-guide mail list], introduce yourself, go find something that needs fixing in the [https://github.com/OWASP/DevGuide/issues GitHub issue list]. Not familiar with git? Get the [https://github.com/OWASP/DevGuide Dev Guide on GitHub] and make edits on your machine, [mailto://bradchesney79@gmail.com 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?
 
; 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!  
+
: Please join the [https://lists.owasp.org/mailman/listinfo/owasp-guide mail list], introduce yourself, go find something that needs writing or missing on [https://github.com/OWASP/DevGuide/wiki/Road-Map-and-Getting-Involved GitHub], write the first draft and mail it to us on the [https://lists.owasp.org/mailman/listinfo/owasp-guide mail list]. We'll take it from there!  
  
 
; How do I get commit privileges on GitHub?
 
; How do I get commit privileges on GitHub?
: Write something for the Guide. Rinse and repeat! :) Or provide so many fixes that we give in and let you have at it directly.  
+
: Fork the [https://github.com/OWASP/DevGuide 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 =
 
= Acknowledgements =
Line 107: Line 112:
 
===Editors===
 
===Editors===
  
 +
* [mailto://bradchesney79@gmail.com Brad Chesney]
 +
* [mailto://steven.van.der.baan@owasp.org Steven Van Der Baan]
 
* Andrew van der Stock
 
* Andrew van der Stock
 
* Abraham Kang
 
* Abraham Kang
Line 124: Line 131:
 
==OWASP Guide 2.0==
 
==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 Andrew van der Stock, vanderaj@owasp.org  
+
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 [mailto://bradchesney79@gmail.com Brad] or [mailto://steven.van.der.baan@owasp.org Steven].
 +
 
  
 
* Abraham Kang
 
* Abraham Kang
Line 163: Line 171:
 
* William Hau
 
* 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.  
+
===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 =
 
= Road Map and Getting Involved =
As of XXX, the priorities are:
+
 
* Starting the re-factor and planning
+
==2015 Planning==
* Authentication - AJV
+
 
* Session Management - TBA
+
* Working out strengths & responsibilities
* Access Control - TBA
+
 
* Input validation and encoding - TBA
+
==Milestone 1 - ==
* Data protection - TBA
+
 
* Cryptography - Kevin Wall
+
==Milestone 2 - ==
 +
 
 +
==Milestone 3 - ==
 +
 
 +
==Milestone 4 - ==
 +
 
 +
==Getting involved==
  
 
Involvement in the development and promotion of Developer Guide is actively encouraged!
 
Involvement in the development and promotion of Developer Guide is actively encouraged!
Line 185: Line 199:
 
* Graphic design
 
* Graphic design
 
* Code snippets in your favorite language
 
* Code snippets in your favorite language
 +
 +
[https://github.com/OWASP/DevGuide/wiki/FAQs See more detailed instructions on the FAQ page.]
  
 
=Project About=
 
=Project About=
{{:Projects/OWASP_Example_Project_About_Page}}
+
{{Template:Project About
 
+
| project_name =OWASP Developer Guide
 +
| project_description =The OWASP Developer Guide is a foundation project, concentrating on how to securely engineer applications
 +
| project_license =CC-BY-SA 3.0
 +
| leader_name1 =Brad Chesney
 +
| leader_email1 =bradchesney79@gmail.com
 +
| leader_name2 =Steven van der Baan
 +
| leader_email2 =steven-van-der-baan@owasp.org
 +
| project_road_map = https://www.owasp.org/index.php/OWASP_Guide_Project#tab=Road_Map_and_Getting_Involved
 +
| leader_username1 = Brad_Chesney
 +
| leader_username2 = Steven_van_der_Baan
 +
| mailing_list_name = https://lists.owasp.org/mailman/listinfo/owasp-guide
 +
}}
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Document]][[Category:SAMM-EG-1]]

Latest revision as of 05:37, 17 March 2016

Lab big.jpg

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.

Presentation

  • TBA

Project Leader

Related Projects

Ohloh

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.

Quick Download

We are developing the Guide in the open 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:


Classifications

Owasp-flagship-icon.jpg
Owasp-builders-small.png
Cc-button-y-sa-small.png
Project Type Files CODE.jpg