Category:OWASP Code Review Project

=Main=



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

Introduction
The code review guide is currently at release version 1.1 and the second best selling OWASP book in 2008. Many positive comments have been feedback regarding this initial version and believe it’s a key enabler for the OWASP fight against software insecurity. It has even inspired individuals to build tools based on its information. The combination of a book on secure code review and tools to support such an activity is very powerful as it gives the developer community a place to start regarding secure application development. Going forward I hope to further integrate with the ASVS and other guides such as the testing and ASDR guides shall be perfromed for version 2.0.t

OWASP Code Review Guide 2.0 Pre-Beta release is now available. It is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that wants good secure code in production.

Gary and I are still in the process of editing content and putting in place with Hugo Costa. Gary and I will also be attending project summary at this years AppSecUSA 2015 in San Francisco. We hope to get some good editing and technical reviews done on the content. Please help by providing technical and grammar feedback to finalize the beta release via email to Larry Conklin or Gary Robinson or to project mailing list or attending project summary.

The project team: Larry Conklin, Johanna Curiel, Michael Hidalgo ,Eoin Keary, Islam Azeddine Mennouchi, Abbas Naderi ,Carlos Pantelides, Ashish Rao, Gary David Robinson, Josh Stroschein ,Colin Watson, Mghazli Zyad

Licensing
OWASP Code Review 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.

Spring Of Code 2007
The Code review guide is proudly sponsored by the OWASP Spring of Code (SpOC) 2007. For more information please see Spring of Code 2007

Summer of Code 2008
The Code review guide is proudly sponsored by the OWASP Summer of Code (SoC) 2008. For more information please see OWASP Summer of Code 2008.


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

What is the Code Review Guide?
OWASP Code Review Guide provides:


 * OWASP Code Review Guide Table of Contents from v1
 * OWASP Code Review V2 Table of Contents

Project Leader

 * Larry Conklin [mailto:larry.conklin@owasp.org]
 * Gary Robinson [mailto:gary.robinson@owasp.org]

Related Projects
OWASP Testing Guide


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

Quick Download

 * Code Review Guide V1.1

Email List
Sign up

News and Events

 * AppSecUSA2015 Project Summit. Join us SEP 22/23, 2015 in Garden Room A (Hyatt Regency)

In Print
Code Review Guide V1.1 on Lulu.

Classifications

 * }

=FAQs=


 * Q1
 * A1


 * Q2
 * A2

= Acknowledgements =

Volunteers
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead. We are actively seeking individuals to add new sections as new web technologies emerge. If you are interested in volunteering for the project, or have a comment, question, or suggestion, please drop me a line [mailto:eoin.keary@owasp.org eoin.keary@owasp.org].

= Road Map and Getting Involved = The project's overall goal is to...

'''be a reference document for the purpose of performing code review. This project shall provide examples in the most common web application development languages (Java and C# .NET)'''

In the near term, we are focused on the following tactical goals...

1. Looking at each attack type and examine the anti-pattern associated with the vulnerability which makes the attack possible. This shall include code examples to guide a reviewer on what to look for.

2. Looking at the code review process, how it is managed and challanges one may encounter when performing code review in the "real world".

3. Looking at the code review tools available and discussing the benefits and issues of using tools.

4. See also Code Review Guide V2.0's Roadmap.

Roadmap for V2:

 * Major enhancements:
 * Introduction to be re-written,
 * Approach to code review (Risk based approach)to be re-written, re designed,
 * Examples by Vulnerability and Technical control to be expanded and refined,
 * Common Numbering nomenclature to be used,
 * Cross reference to TG and ASVS to be done,
 * New sections on tools to be introduced,
 * Expand technology specific sections,
 * Section on RIA (Rich Internet applications) to be introduced,
 * WebServices section to be refined,
 * Malware and rootkit sections to be introduced,
 * PCI section to be rewritten with more x-reference to other guides.


 * Other ideas:
 * ESAPI section: how to review OWASP ESAPI implementations?
 * Risk based approach Vs ASVS levels,
 * Threat modeling and Triage chapters to be revised,
 * OWASP O2 section on O2 rules definition, development,
 * Crawling code: Additional search vectors to be added,
 * Section on Code Crawler, quick start & configuration guide.

Get Involved
All of the OWASP Guides are living documents that will continue to change as the threat and security landscape changes. We welcome everyone to join the Code Review Guide Project and help us make this document great. The best way to get started is to subscribe to the mailing list by following the link below. Please introduce yourself and ask to see if there is anything you can help with. We are always looking for new contributions. If there is a topic that you’d like to research and contribute, please let us know!

=Project About=