Testing: Introduction and objectives - Revision history

Andrew Muller: Change Data Validation to Input Validation

2014-08-05T15:25:44Z

Change Data Validation to Input Validation

Jane O'Connor: Added Andrew's changes.

2014-08-01T18:13:07Z

Added Andrew's changes.

Jane O'Connor: Final edit

2014-05-13T09:17:51Z

Final edit

Davide Danelon at 16:51, 4 March 2014

2014-03-04T16:51:54Z

Mmeucci at 14:39, 9 October 2012

2012-10-09T14:39:12Z

Mmeucci at 15:11, 12 March 2009

2009-03-12T15:11:05Z

KirstenS at 13:38, 2 February 2009

2009-02-02T13:38:19Z

KirstenS at 13:37, 2 February 2009

2009-02-02T13:37:56Z

KirstenS at 13:46, 26 November 2008

2008-11-26T13:46:45Z

Mmeucci at 15:17, 25 September 2008

2008-09-25T15:17:18Z

@@ Line 75: / Line 75: @@
 The set of active tests have been split into 11 sub-categories for a total of 91 controls:
 * Information Gathering
-* Configuration and Deploy Management Testing
+* Configuration and Deployment Management Testing
 * Identity Management Testing
 * Authentication Testing
 * Authorization Testing
 * Session Management Testing
-* Data Validation Testing
+* Input Validation Testing
 * Error Handling
 * Cryptography
 * Business Logic Testing
 * Client Side Testing

@@ Line 1: / Line 1: @@
 {{Template:OWASP Testing Guide v4}}
-This section describes the OWASP web application penetration testing methodology and explains how to test each vulnerability.
+This section describes the OWASP web application security testing methodology and explains how to test for evidence of vulnerabilities within the application due to deficiencies with identified security controls.
-'''What is a Vulnerability?'''<br>
-A vulnerability is a flaw or weakness in a system's design, implementation, operation or management that could be exploited to violate the system's security policy. A threat is a potential attack that may harm the assets owned by an application (resources of value, such as the data in a database or in the file system) by exploiting a vulnerability. A test is an action that tends to show a vulnerability in the application.
+'''What is a Threat?'''<br>
@@ Line 22: / Line 29: @@
 * Consistent
 * Reproducible
 * Under quality control<br>
-The problems to be addressed are fully documented and tested. It is important to use a method to test all known vulnerabilities and document all the penetration test activities.<br>
+The problems to be addressed are fully documented and tested. It is important to use a method to test all known vulnerabilities and document all the security test activities.<br>
 '''What is the OWASP testing methodology?'''<br>
-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. The goal of this project is to collect all the possible testing techniques, explain these techniques, and keep the guide updated. The OWASP Web Application Penetration Testing method is based on the black box approach. The tester knows nothing or has very little information about the application to be tested.
+Security testing will never be an exact science where a complete list of all possible issues that should be tested can be defined. Indeed, security testing is only an appropriate technique for testing the security of web applications under certain circumstances. The goal of this project is to collect all the possible testing techniques, explain these techniques, and keep the guide updated. The OWASP Web Application Security Testing method is based on the black box approach. The tester knows nothing or has very little information about the application to be tested.

@@ Line 1: / Line 1: @@
 {{Template:OWASP Testing Guide v4}}
-This Chapter describes the OWASP Web Application Penetration testing methodology and explains how to test each vulnerability.
+This section describes the OWASP web application penetration testing methodology and explains how to test each vulnerability.
 '''What is Web Application Penetration Testing?'''<br>
-A penetration test is a method of evaluating the security of a computer system or network by simulating an attack. A Web Application Penetration Test focuses only on evaluating the security of a web application.<br>
+A penetration test is a method of evaluating the security of a computer system or network by simulating an attack. A web application penetration test focuses 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 the impact, a proposal for mitigation or a technical solution.
-A vulnerability is a flaw or weakness in a system's design, implementation, or operation and management that could be exploited to violate the system's security policy.
+'''What is a Vulnerability?'''<br>
-A threat is a potential attack that, by exploiting a vulnerability, may harm the assets owned by an application (resources of value, such as the data in a database or in the file system).
+A vulnerability is a flaw or weakness in a system's design, implementation, operation or management that could be exploited to violate the system's security policy. A threat is a potential attack that may harm the assets owned by an application (resources of value, such as the data in a database or in the file system) by exploiting a vulnerability. A test is an action that tends to show a vulnerability in the application.
-The OWASP approach is Open and Collaborative:
+'''The Approach in Writing this Guide'''
 * Open: every security expert can participate with his or her experience in the project. Everything is free.
-* Collaborative: we usually perform brainstorming before the articles are written so we can share our ideas and develop a collective vision of the project. That means rough consensus, wider audience and participation.<br>
+* Collaborative: brainstorming is performed before the articles are written so the team can share ideas and develop a collective vision of the project. That means rough consensus, a wider audience and increased participation.<br>
 This approach tends to create a defined Testing Methodology that will be:
 * Consistent
 * Reproducible
 * Under quality control<br>
-The problems that we want to be addressed are:
-* Document all
-* Test all
+The problems to be addressed are fully documented and tested. It is important to use a method to test all known vulnerabilities and document all the penetration test activities.<br>
-We think it is important to use a method to test all known vulnerabilities and document all the pen test activities.<br>
 '''What is the OWASP testing methodology?'''<br>
-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.
+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. The goal of this project is to collect all the possible testing techniques, explain these techniques, and keep the guide updated. The OWASP Web Application Penetration Testing method is based on the black box approach. The tester knows nothing or has very little information about the application to be tested.
-The goal is to collect all the possible testing techniques, explain them, and keep the guide updated.<br>
 The OWASP Web Application Penetration Testing method is based on the black box approach. The tester knows nothing or very little information about the application to be tested.
 The testing model consists of:
 * Tester: Who performs the testing activities
 * Tools and methodology: The core of this Testing Guide project
 * Application: The black box to test
 The test is divided into 2 phases:
-* Passive mode: in the passive mode, the tester tries to understand the application's logic, and plays with the application. Tools can be used for information gathering, for example, an HTTP proxy to observe all the HTTP requests and responses. At the end of this phase, the tester should understand all the access points (''gates'') of the application (e.g., HTTP headers, parameters, and cookies). The Information Gathering section explains how to perform a passive mode test. For example, the tester could find the following:
+* Phase 1 Passive mode:
 <pre>
 https://www.example.com/login/Authentic_Form.html
 </pre>
-This may indicate an authentication form in which the application requests a username and a password. <br>
 The following parameters represent two access points (gates) to the application:
 <pre>
 http://www.example.com/Appx.jsp?a=1&b=1
 </pre>
 In this case, the application shows two gates (parameters a and b).
-All the gates found in this phase represent a point of testing. A spreadsheet with the directory tree of the application and all the access points would be useful for the second phase.<br> <br>
+All the gates found in this phase represent a point of testing. A spreadsheet with the directory tree of the application and all the access points would be useful for the second phase.
-* Active mode: in this phase, the tester begins to test using the methodology described in the follow paragraphs.
-We have split the set of active tests in 12 sub-categories for a total of 91 controls:
+The set of active tests have been split into 11 sub-categories for a total of 91 controls:
 * Information Gathering
 * Configuration and Deploy Management Testing
@@ Line 60: / Line 75: @@
 * Error Handling
 * Cryptography
 * Business Logic Testing
 * Client Side Testing

@@ Line 50: / Line 50: @@
 * Active mode: in this phase, the tester begins to test using the methodology described in the follow paragraphs.
-We have split the set of active tests in 9 sub-categories for a total of 66 controls:
+We have split the set of active tests in 12 sub-categories for a total of 91 controls:
-* Configuration Management Testing
+* Information Gathering
 * Business Logic Testing
-* Authentication Testing
+* Client Side Testing

← Older revision		Revision as of 14:39, 9 October 2012
Line 1:		Line 1:
−	{{Template:OWASP Testing Guide v3}}	+	{{Template:OWASP Testing Guide v4}}

	This Chapter describes the OWASP Web Application Penetration testing methodology and explains how to test each vulnerability.		This Chapter describes the OWASP Web Application Penetration testing methodology and explains how to test each vulnerability.

@@ Line 54: / Line 54: @@
 * Business Logic Testing
 * Authentication Testing
 * Authorization testing
 * Data Validation Testing
 * Denial of Service Testing
 * Web Services Testing
 * Ajax Testing

← Older revision		Revision as of 13:38, 2 February 2009
Line 60:		Line 60:
	* Web Services Testing		* Web Services Testing
	* Ajax Testing		* Ajax Testing
−
−	~~The following paragraphs describe the set of checklists that compose the methodology.~~