OWASP Code Review Guide

![_lab_big.jpg](_lab_big.jpg "_lab_big.jpg")

Code Review Guide

Please forward to all the developers and development teams you know

</td>

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.

</td>
  • Larry Conklin 1
  • Gary Robinson 2

Project Email

  • Project Email 3

Classifications

Owasp-defenders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Cc-button-y-sa-small.png
Project_Type_Files_DOC.jpg
Project_Type_Files_DOC.jpg

OWASP Testing Guide 4

</td>

In Print

Code Review Guide 2.0 will be available in Lulu in the near future.

Code Review Guide V1.1 on Lulu.

</td>

We would like to immediately start raising awareness about this OWASP resource. We plan to release the final version in Aug. 2017 after a public comment period ending July 31, 2017.

Thank you, Larry Conklin, Gary Robinson OWASP Code Review Guides Co-Leaders

Thank you, Larry Conklin, Gary Robinson OWASP Code Review Guides Co-Leaders

Introduction

Introduction

OWASP Code Review Guide 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 to 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 desires good secure code in production.

OWASP Code Review Guide 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 to 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 desires good secure code in production.

Second sections deals with vulnerabilities. It is based on the poplar OWASP 2013 top 10. Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in "Object-Oriented Programming" and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.

Second sections deals with vulnerabilities. It is based on the poplar OWASP 2013 top 10. Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in "Object-Oriented Programming" and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.

The last section is the appendix. Here we have content like code reviewer check list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.

The last section is the appendix. Here we have content like code reviewer check list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.

Review of Code Review Guide 2.0

Review of Code Review Guide 2.0

Constructive comments on this OWASP Code Review Release Candidate should be forwarded via email to [email protected] Private comments may be sent to [email protected] or [email protected] . All comments are welcome. All comments should indicate the specific relevant page and section.

Constructive comments on this OWASP Code Review Release Candidate should be forwarded via email to [email protected] Private comments may be sent to [email protected] or [email protected] . All comments are welcome. All comments should indicate the specific relevant page and section.

All feedback is critical to the continued success of the OWASP Code Review Guide.

All feedback is critical to the continued success of the OWASP Code Review Guide.

Licensing

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.

Acknowledgements

The OWASP Code Review project was conceived by Eoin Keary, the OWASP Dublin Founder and Chapter Lead.

Code Review Mailing list5

Project leaders [email protected] or [email protected]

NOTOC

Category:OWASP Project Category:OWASP_Defenders Category:OWASP_Document


Example

Put whatever you like here: news, screenshots, features, supporters, or remove this file and don’t use tabs at all.