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 "The Owasp Code Review Top 9"

From OWASP
Jump to: navigation, search
m
Line 5: Line 5:
 
== Preface ==
 
== Preface ==
 
In this section, we will try to organize the most critical security flaws you can find during a code review in order to have a finite set of categories to evaluate the whole code review process.
 
In this section, we will try to organize the most critical security flaws you can find during a code review in order to have a finite set of categories to evaluate the whole code review process.
 +
 +
''needs more details here''
 +
 +
== The 7 flaw categories ==
 +
In term of source code security, source code vulnerabilities can be managed in million of ways.
 +
 +
Source code vulnerabilities must reflect Owasp Top 10 recommendations. Applications are made of source so, in some way source code flaws can be re conducted to flaws in application.
 +
 +
''needs more details here''
 +
 +
Here you can find the seventh source code flaw categories:
 +
 +
* Input validation
 +
* Source code design
 +
* Information leakage and improper error handling
 +
* Direct object reference
 +
* Resource usage
 +
* API usage
 +
* Best practices violation

Revision as of 13:38, 4 June 2008

OWASP Code Review Guide Table of Contents


Preface

In this section, we will try to organize the most critical security flaws you can find during a code review in order to have a finite set of categories to evaluate the whole code review process.

needs more details here

The 7 flaw categories

In term of source code security, source code vulnerabilities can be managed in million of ways.

Source code vulnerabilities must reflect Owasp Top 10 recommendations. Applications are made of source so, in some way source code flaws can be re conducted to flaws in application.

needs more details here

Here you can find the seventh source code flaw categories:

  • Input validation
  • Source code design
  • Information leakage and improper error handling
  • Direct object reference
  • Resource usage
  • API usage
  • Best practices violation