Difference between revisions of "Testing: Introduction and objectives"

Revision as of 14:39, 19 October 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

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.