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 "Chapters Assigned"

From OWASP
Jump to: navigation, search
(Design review)
 
(17 intermediate revisions by 5 users not shown)
Line 4: Line 4:
 
#Steps and Roles
 
#Steps and Roles
 
#Code Review Processes
 
#Code Review Processes
 +
#Transaction Analysis - E Keary
  
 
== Design review ==
 
== Design review ==
 
#Designing for security  
 
#Designing for security  
 
## - M Roxberry(.NET)
 
## - M Roxberry(.NET)
## - P Perego (Java)
+
## - Paolo Perego (Java)
## - PHP
+
## - Andrew van der Stock (PHP)
## - P Perego (C)
+
## - Paolo Perego (C)
 
## - C++
 
## - C++
## - MySQL
+
## - Andrew van der Stock (MySQL)
 +
## - Mallory (AJAX)
  
 
==Examples by Vulnerability==
 
==Examples by Vulnerability==
#Reviewing Code for Buffer Overruns and Overflows - 70%
+
#Reviewing Code for Buffer Overruns and Overflows - 100%
#Reviewing Code for OS Injection - 70%
+
#Reviewing Code for OS Injection - 100%
#Reviewing Code for SQL Injection - 70%
+
#Reviewing Code for SQL Injection - 100%
#Reviewing Code for Data Validation - 70%
+
#Reviewing Code for Data Validation - - 100%
#Reviewing Code for Error Handling - 70%
+
#Reviewing code for XSS issues - 100%
#Reviewing Code for Logging Issues - 70%
+
#Reviewing Code for Error Handling - 100%
#Reviewing The Secure Code Environment - E Keary
+
#Reviewing Code for Logging Issues - 100%
#Transaction Analysis - E Keary
+
#Reviewing The Secure Code Environment - 100%
 
#Authorization (Currently linked to "The Development Guide")
 
#Authorization (Currently linked to "The Development Guide")
 
#Authentication (Code review)
 
#Authentication (Code review)
Line 28: Line 30:
 
#Cross Site Request Forgery
 
#Cross Site Request Forgery
 
#Cryptography (Currently linked to "The Development Guide")
 
#Cryptography (Currently linked to "The Development Guide")
#Dangerous HTTP Methods
+
#Dangerous HTTP Methods ( Secure deployment)
 
#Race Conditions
 
#Race Conditions
 +
  
 
== Language specific best practice ==
 
== Language specific best practice ==
  
===Java===
 
#Inner classes
 
#Class comparison
 
#Cloneable classes
 
#Serializable classes
 
#Package scope and encapsulation
 
#Mutable objects
 
#Private methods & circumvention
 
 
===.NET===
 
===.NET===
  
 
===PHP===
 
===PHP===
 +
 +
Assigned to Andrew van der Stock
  
 
===MySQL===
 
===MySQL===
  
===Stored Procs===
+
Assigned to Andrew van der Stock
  
===C===
+
===C/C++===
===C++===
+
 
 +
# Memory management (Paolo Perego)
 +
# String management (Paolo Perego)
 +
# Secure access to file system items (Paolo Perego)
  
 
==Automating Code Reviews==
 
==Automating Code Reviews==
Line 57: Line 57:
 
#Education and cultural change
 
#Education and cultural change
 
#Tool Deployment Model
 
#Tool Deployment Model
 
+
#Code Auditor Workbench Tool (100%)
 
==References==
 
==References==

Latest revision as of 11:17, 23 October 2007

Methodology

  1. Code Review Introduction
  2. Steps and Roles
  3. Code Review Processes
  4. Transaction Analysis - E Keary

Design review

  1. Designing for security
    1. - M Roxberry(.NET)
    2. - Paolo Perego (Java)
    3. - Andrew van der Stock (PHP)
    4. - Paolo Perego (C)
    5. - C++
    6. - Andrew van der Stock (MySQL)
    7. - Mallory (AJAX)

Examples by Vulnerability

  1. Reviewing Code for Buffer Overruns and Overflows - 100%
  2. Reviewing Code for OS Injection - 100%
  3. Reviewing Code for SQL Injection - 100%
  4. Reviewing Code for Data Validation - - 100%
  5. Reviewing code for XSS issues - 100%
  6. Reviewing Code for Error Handling - 100%
  7. Reviewing Code for Logging Issues - 100%
  8. Reviewing The Secure Code Environment - 100%
  9. Authorization (Currently linked to "The Development Guide")
  10. Authentication (Code review)
  11. Session Integrity
  12. Cross Site Request Forgery
  13. Cryptography (Currently linked to "The Development Guide")
  14. Dangerous HTTP Methods ( Secure deployment)
  15. Race Conditions


Language specific best practice

.NET

PHP

Assigned to Andrew van der Stock

MySQL

Assigned to Andrew van der Stock

C/C++

  1. Memory management (Paolo Perego)
  2. String management (Paolo Perego)
  3. Secure access to file system items (Paolo Perego)

Automating Code Reviews

  1. Preface
  2. Reasons for using automated tools
  3. Education and cultural change
  4. Tool Deployment Model
  5. Code Auditor Workbench Tool (100%)

References