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 "Testing: Introduction and objectives"
| Line 41: | Line 41: | ||
|| Information Gathering || || Application Discovery || || || || | || Information Gathering || || Application Discovery || || || || | ||
|- | |- | ||
| − | || || Spidering and googling | + | || || || Spidering and googling || || || || |
|- | |- | ||
| − | || || Analisys of error code | + | || || || Analisys of error code || || || || |
|- | |- | ||
| − | || || SSL/TLS Testing | + | || || || SSL/TLS Testing || || || || |
|- | |- | ||
| − | || || DB Listener Testing | + | || || || DB Listener Testing || || || || |
|- | |- | ||
| − | || || File extensions handling | + | || || || File extensions handling || || || || |
|- | |- | ||
| − | || || Old, backup and unreferenced files | + | || || || Old, backup and unreferenced files || || || || |
|- | |- | ||
| − | ||Business logic testing || || || || || | + | ||Business logic testing || || || || || || |
| + | |- | ||
| + | || || || || || || || | ||
|- | |- | ||
|| Authentication Testing || || || || || <u>http://www.owasp.org</u> || | || Authentication Testing || || || || || <u>http://www.owasp.org</u> || | ||
|- | |- | ||
| + | || || || Default or guessable account || || || || | ||
| + | |- | ||
| + | || || || Brute Force || || || || | ||
| + | |- | ||
| + | || || || Bypassing authentication schema || || || || | ||
| + | |- | ||
| + | || || || Directory traversal/file include || || || || | ||
| + | |- | ||
| + | || || || Vulnerable remember password and pwd reset || || || || | ||
| + | |- | ||
| + | || || || Logout and Browser Cache Management Testing || || || || | ||
| + | |- | ||
| + | || || || || || || || | ||
| + | |- | ||
| + | |||
|| Session Management Testing || || || || || <u>http://www.owasp.org</u> || | || Session Management Testing || || || || || <u>http://www.owasp.org</u> || | ||
|- | |- | ||
Revision as of 14:59, 3 November 2006
[Up]
OWASP Testing Guide v2 Table of Contents
This Chapter describes the OWASP Web Application Penetration testing methology and explains how to test each vulnerabilities.
What is Web Application Penetration Testing?
A penetration test is a method of evaluating the security of a computer system or network by simulating an attack. A Web Application Penetration Testing focalize only on evaluating the security of a web application.
The process involves an active analysis of the application for any weaknesses, technical flaws or vulnerabilities. Any security issues that are found will be presented to the system owner together with an assessment of their impact and often with a proposal for mitigation or a technical solution.
What is a vulnerability?
Given an application that own a set of assets (resources of value such as the data in a database or on the file system), a vulnerability is a weakness on a asset that makes a threat possible. So a threat is a potential occurrence that may harm an asset exploiting Vulnerability. A test is an action that tends to show a vulnerability in the application
What is the list of OWASP testing?
Penetration testing will never be an exact science where a complete list of all possible issues that should be tested can be defined. Indeed, penetration testing is only an appropriate technique for testing the security of web applications under certain circumstances. Our goal is to collect all the possible testing techniques, explain it and mantain it updated.
Our approach
Collaborative
Open
- Information Gathering
- Business logic testing
- Authentication Testing
- Session Management Testing
- Data Validation Testing
- Denial of Service Testing
- Web Services Testing
- AJAX Testing
...here: List of test
| Category | Ref Number | Name | Finding | Affected Item | Comment/Solution | Risk Value |
| Information Gathering | Application Discovery | |||||
| Spidering and googling | ||||||
| Analisys of error code | ||||||
| SSL/TLS Testing | ||||||
| DB Listener Testing | ||||||
| File extensions handling | ||||||
| Old, backup and unreferenced files | ||||||
| Business logic testing | ||||||
| Authentication Testing | http://www.owasp.org | |||||
| Default or guessable account | ||||||
| Brute Force | ||||||
| Bypassing authentication schema | ||||||
| Directory traversal/file include | ||||||
| Vulnerable remember password and pwd reset | ||||||
| Logout and Browser Cache Management Testing | ||||||
| Session Management Testing | http://www.owasp.org | |||||
| Data Validation Testing | http://www.owasp.org | |||||
| Denial of Service Testing | http://www.owasp.org | |||||
| Web Services Testing | http://www.owasp.org | |||||
| AJAX Testing | http://www.owasp.org |
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
