Difference between revisions of "Chapters Assigned"

From OWASP
Jump to: navigation, search
(C)
(Design review)
Line 8: Line 8:
 
#Designing for security  
 
#Designing for security  
 
## - M Roxberry(.NET)
 
## - M Roxberry(.NET)
## - (Java)
+
## - Paolo Perego (Java)
 
## - PHP
 
## - PHP
 
## - C/C++
 
## - C/C++

Revision as of 10:35, 17 January 2007

Contents

Methodology

  1. Code Review Introduction
  2. Steps and Roles
  3. Code Review Processes

Design review

  1. Designing for security
    1. - M Roxberry(.NET)
    2. - Paolo Perego (Java)
    3. - PHP
    4. - C/C++
    5. - MySQL

Examples by Vulnerability

  1. Reviewing Code for Buffer Overruns and Overflows - 70%
  2. Reviewing Code for OS Injection - 70%
  3. Reviewing Code for SQL Injection - 70%
  4. Reviewing Code for Data Validation - 70%
  5. Reviewing Code for Error Handling - 70%
  6. Reviewing Code for Logging Issues - 70%
  7. Reviewing The Secure Code Environment - E Keary
  8. Transaction Analysis - E Keary
  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
  15. Race Conditions

Language specific best practice

Java

  1. Inner classes (Paolo Perego)
  2. Class comparison (Paolo Perego)
  3. Cloneable classes (Paolo Perego)
  4. Serializable classes (Paolo Perego)
  5. Package scope and encapsulation (Paolo Perego)
  6. Mutable objects (Paolo Perego)
  7. Private methods & circumvention (Paolo Perego)

.NET

PHP

MySQL

Stored Procs

C

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

C++

Automating Code Reviews

  1. Preface
  2. Reasons for using automated tools
  3. Education and cultural change
  4. Tool Deployment Model

References