to do this, you would need to use client credentials through the tunnel you just created, and provide the client subnet to route traffic correctly through that "VPN": sshuttle -r user@localhost:2200 192.168.1.0/24 once this tunnel is created, you should be able to access any resource on the remote network by its IP and port (for example, through the browser for http(s)) An additional thing that one might want to do is making the connection from C to S passwordless and automatic (this can be accomplished with tools or scripts readily available on the internet). WARNING: Make sure to remove/clean any persistent connections once you are done with auditing. There should be no need for multiple reverse tunnels, as multiple forward tunnels can be set up from S to C if needed (eg. VNC or RDP); this requires multiple forward tunnels from A to S though. Scenario 2 Legend: A: Auditee's local machine; a clean machine, connected to the Internet through the auditee's LAN network B: Auditor machine Someone at the auditee's side will prepare machine A in coordination with the auditor, then install TeamViewer. After that, and using a trusted communication method, TeamViewer ID and passcode will be sent to the Auditor. The auditor will use the ID and passcode to connect to the machine and start using machine A as the auditing machine. There are pros and cons for this: Cons: 1. Internet speed: You will need a high speed Internet connection to achieve such task, as the remote access will be transferring the desktop of the targeted machine to you Page 65 of 240