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 "Identify application exit/handover points (OTG-INFO-007)"
From OWASP
m (moved Testing Identify application exit/handover points (OWASP-IG-008) to Identify application exit/handover points (OTG-INFO-007): Align with common numbering effort and clarify purpose of test case) |
|||
| Line 1: | Line 1: | ||
{{Template:OWASP Testing Guide v4}} | {{Template:OWASP Testing Guide v4}} | ||
| − | == | + | == Summary == |
Some applications defer functionality to other existing applications. A common example of this is the payment gateway. Many application owners don't wish to incur the cost and hassle of maintaining their own application payment gateway, so they leverage existing payment gateway providers to handle payments for their applications. | Some applications defer functionality to other existing applications. A common example of this is the payment gateway. Many application owners don't wish to incur the cost and hassle of maintaining their own application payment gateway, so they leverage existing payment gateway providers to handle payments for their applications. | ||
| − | == | + | == Test Objectives == |
| + | The objectives of this test case are: | ||
| + | * to clarify the scope of the test, and | ||
| + | * to understand the state/circumstances of normal termination of the application, and | ||
| + | * to observe what parameters and information is exchanged during the application handover. | ||
| + | == How to Test == | ||
| − | + | ''' Black Box testing and example ''' | |
| − | + | ''' Gray Box testing and example ''' | |
| − | + | ||
| + | |||
| + | == Tools == | ||
| + | |||
| + | * Wget | ||
| + | * Httprint | ||
== References == | == References == | ||
| Line 18: | Line 28: | ||
[1] http://net-square.com/httprint.html HTTPrint download page | [1] http://net-square.com/httprint.html HTTPrint download page | ||
| − | + | == Remediation == | |
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 13:42, 28 July 2013
This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table_of_Contents Back to the OWASP Testing Guide Project: https://www.owasp.org/index.php/OWASP_Testing_Project
Summary
Some applications defer functionality to other existing applications. A common example of this is the payment gateway. Many application owners don't wish to incur the cost and hassle of maintaining their own application payment gateway, so they leverage existing payment gateway providers to handle payments for their applications.
Test Objectives
The objectives of this test case are:
- to clarify the scope of the test, and
- to understand the state/circumstances of normal termination of the application, and
- to observe what parameters and information is exchanged during the application handover.
How to Test
Black Box testing and example
Gray Box testing and example
Tools
- Wget
- Httprint
References
Whitepapers [1] http://net-square.com/httprint.html HTTPrint download page
