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"
Brad Chesney (talk | contribs) m |
Brad Chesney (talk | contribs) (Links to the pertinent pages for action.) |
||
| Line 90: | Line 90: | ||
; 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 Q2 2014. If we get more volunteers, sooner. | + | : We are hoping to have the [https://github.com/OWASP/DevGuide/wiki/Road-Map-and-Getting-Involved#wiki-milestone-1---april-30-2014 first milestone], consisting of the Authentication, Session Management, Access Control, Input validation and output encoding, and Data Protection chapters complete by Q2 2014. If we get more volunteers, sooner. |
; 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] and then fix it and mail it back to us. We'll take it from there! |
; 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. | + | : Write something for the Guide and send a pull request. Rinse and repeat! :) Or provide so many fixes that we give in and let you have at it directly. |
= Acknowledgements = | = Acknowledgements = | ||
Revision as of 07:16, 4 February 2014
OWASP Developer GuideThe 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. IntroductionThe 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:
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 audienceThe 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
Project Leader
Related ProjectsLicensingOWASP 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 DownloadWe 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
In PrintVersion 2.0.1 can be purchased for historical research on Lulu.com:
Classifications
| |||||||
