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
Identify application exit/handover points (OTG-INFO-007)
From OWASP
Revision as of 02:04, 13 June 2013 by Andrew Muller (talk | contribs) (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)
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
Brief 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.
Description of the Issue
Black Box testing and example
Gray Box testing and example
Not applicable.
References
Whitepapers [1] http://net-square.com/httprint.html HTTPrint download page
Tools
- Wget
- Httprint
