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
(→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 15:35, 17 January 2007
Methodology
- Code Review Introduction
- Steps and Roles
- Code Review Processes
Design review
- Designing for security
- - M Roxberry(.NET)
- - Paolo Perego (Java)
- - PHP
- - C/C++
- - MySQL
Examples by Vulnerability
- Reviewing Code for Buffer Overruns and Overflows - 70%
- Reviewing Code for OS Injection - 70%
- Reviewing Code for SQL Injection - 70%
- Reviewing Code for Data Validation - 70%
- Reviewing Code for Error Handling - 70%
- Reviewing Code for Logging Issues - 70%
- Reviewing The Secure Code Environment - E Keary
- Transaction Analysis - E Keary
- Authorization (Currently linked to "The Development Guide")
- Authentication (Code review)
- Session Integrity
- Cross Site Request Forgery
- Cryptography (Currently linked to "The Development Guide")
- Dangerous HTTP Methods
- Race Conditions
Language specific best practice
Java
- Inner classes (Paolo Perego)
- Class comparison (Paolo Perego)
- Cloneable classes (Paolo Perego)
- Serializable classes (Paolo Perego)
- Package scope and encapsulation (Paolo Perego)
- Mutable objects (Paolo Perego)
- Private methods & circumvention (Paolo Perego)
.NET
PHP
MySQL
Stored Procs
C
- Memory management (Paolo Perego)
- String management (Paolo Perego)
- Secure access to file system items (Paolo Perego)
C++
Automating Code Reviews
- Preface
- Reasons for using automated tools
- Education and cultural change
- Tool Deployment Model