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 "OWASP Code Review Guide Table of Contents"
From OWASP
(→Methodology) |
|||
Line 66: | Line 66: | ||
#[[AJAX Applications]] | #[[AJAX Applications]] | ||
#[[Web Services]] | #[[Web Services]] | ||
+ | |||
+ | == Example reports == | ||
+ | #[[How to write]] | ||
+ | #[[How to determine the risk level of a finding]] | ||
+ | #[[Sample form]] | ||
==[[Automating Code Reviews]]== | ==[[Automating Code Reviews]]== |
Revision as of 01:39, 2 May 2008
Foreword by OWASP Chair
1. Frontispiece
1.1 About the OWASP Code Review Project
1.2 About The Open Web Application Security Project
Guide History
Methodology
- Introduction
- Steps and Roles
- Code Review Processes
- Transaction Analysis
- How to write an application_security finding
- Applicaiton Threat Modeling
- The Round Trip Code Review
- Code review Metrics
Crawling Code
Examples by Vulnerability
- Reviewing Code for Buffer Overruns and Overflows
- Reviewing Code for OS Injection
- Reviewing Code for SQL Injection
- Reviewing Code for Data Validation
- Reviewing code for XSS issues
- Reviewing code for Cross-Site Request Forgery issues
- Reviewing Code for Error Handling
- Reviewing Code for Logging Issues
- Reviewing The Secure Code Environment
- Reviewing Code for Authorization Issues
- Reviewing Code for Authentication
- Reviewing Code for Session Integrity issues
- Reviewing Cryptographic Code
- Reviewing Code for Race Conditions
Language specific best practice
Java
PHP
C/C++
MySQL
Rich Internet Applications
Example reports
Automating Code Reviews
- Preface
- Reasons for using automated tools
- Education and cultural change
- Tool Deployment Model
- Code Auditor Workbench Tool
- The Owasp Orizon Framework
Ways to achieve secure code on a budget