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 for HTTP Incoming requests (OTG-INPVAL-017)"
(→References) |
(→TCP-level Network Traffic Capture) |
||
Line 26: | Line 26: | ||
=== TCP-level Network Traffic Capture === | === TCP-level Network Traffic Capture === | ||
This technique monitor all the network traffic at TCP-level. | This technique monitor all the network traffic at TCP-level. | ||
− | TCPDump or WireShark tools can be used. However, these tools don't allow us edit the captured traffic and send modified http requests for testing. | + | TCPDump or WireShark tools can be used. However, these tools don't allow us edit the captured traffic and send modified http requests for testing. To replay the captured traffic (PCAP) packets, Ostinato can be used. |
+ | |||
+ | The testing steps will be: | ||
+ | |||
+ | 1. Activate TCPDump or WireShark on Web Server side to capture network traffic | ||
+ | 2. Monitor the captured files (PCAP) | ||
+ | 3. Edit PCAP files by Ostinato tool based on need | ||
+ | 4. Reply the http requests | ||
== Tools == | == Tools == |
Revision as of 23:31, 9 April 2016
Summary
This section describes how to monitor all incoming/outgoing http requests on both client or web server side. The purpose of this testing is to verify if there is unnecessary or suspicious http request sending in the background.
Most of Web security testing tools (i.e. AppScan, BurpSuite, ZAP) act as Http Proxy. This will require changes of proxy on client side application or browser. The testing techniques listed below is primary focused on how we can monitor Http requests without changes of client side which will be more close to production usage scenario.
Test Objectives
1. Monitor all incoming and outgoing http requests to the Web Server to inspect any suspicious requests.
2. Monitor http traffic without changes of end user Browser proxy or client-side application.
How to Test
Reverse Proxy
There is situation that we would like to monitor all http incoming requests on web server side but we can't change configuration on browser or application client side. In this scenario, we can setup reverse proxy on web server side to monitor all incoming/outgoing requests on web server side.
For windows platform, Fiddler is recommended. It provides not only monitor but can also edit/reply the http requests. Refer the refernece for how to configure fiddler as reverse Proxy.
http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/UseFiddlerAsReverseProxy
For Linux platform, Charles Web Debugging Proxy may be used.
Port Forwarding
TCP-level Network Traffic Capture
This technique monitor all the network traffic at TCP-level. TCPDump or WireShark tools can be used. However, these tools don't allow us edit the captured traffic and send modified http requests for testing. To replay the captured traffic (PCAP) packets, Ostinato can be used.
The testing steps will be:
1. Activate TCPDump or WireShark on Web Server side to capture network traffic 2. Monitor the captured files (PCAP) 3. Edit PCAP files by Ostinato tool based on need 4. Reply the http requests
Tools
- Fiddler
- TCPProxy
- Charles Web Debugging Proxy
- WireShark
- PowerEdit-Pcap
- WireEdit
- pcapteller
- replayproxy
- Ostinato