Difference between revisions of "Category:OWASP Code Review Project"

Q1

A1

Q2

A2

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 [email protected].

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!