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
Category:OWASP Code Review Project
![]() |
This project is part of the OWASP Defenders community. Feel free to browse other projects within the Defenders, Builders, and Breakers communities. |
![]() |
This project has produced a book that can be downloaded or purchased. Feel free to browse the full catalog of available OWASP books. |
The Release Candidate for the OWASP Code Review Guide is now available!Please forward to all the developers and development teams you know!! 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 IntroductionOWASP 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”. 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.0Constructive comments on this OWASP Top 10 - 2017 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. LicensingOWASP 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.
|
Project LeaderRelated ProjectsOWASP Testing Guide [3]
|
Quick DownloadIn PrintCode Review Guide 2.0 will be available in Lulu in the near future. Code Review Guide V1.1 on Lulu. |
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead. Current project leaders are Larry Conklin and Gary Robinson.
Code Review Mailing list[4]
Project leaders [email protected] or [email protected]
Pages in category "OWASP Code Review Project"
The following 69 pages are in this category, out of 69 total.
C
- Classic ASP Design Mistakes
- Code Review Guide Foreword
- Code Review Guide Frontispiece
- Code Review Introduction
- Code Review Metrics
- Code Review Preparation
- Code Reviews and Compliance
- Codereview-Authentication
- Codereview-Authorization
- Codereview-Cryptography
- Codereview-Deployment
- Codereview-Error-Handling
- Codereview-Input Validation
- Codereview-Session-Management
- Crawling Code
- CRV2 ErrorHandlingMessages
- CRV2 MetricsCodeRev
- CRV2 PrepContext
- CRV2 SQLInjPHP
O
R
- Reasons for using automated tools
- References
- Reviewing Code for Authentication
- Reviewing Code for Authorization Issues
- Reviewing Code for Buffer Overruns and Overflows
- Reviewing code for Cross-Site Request Forgery issues
- Reviewing Code for Cross-site scripting
- Reviewing Code for Data Validation
- Reviewing Code for Error Handling
- Reviewing Code for Logging Issues
- Reviewing Code for OS Injection
- Reviewing Code for Race Conditions
- Reviewing Code for Session Integrity issues
- Reviewing Code for SQL Injection
- Reviewing Flash Applications
- Reviewing MySQL Security
- Reviewing The Secure Code Environment
- Reviewing Web Services