Would it make a difference knowing the product behind the sniffing? Once your traffic went on the clear and there&#x27;s people with access to it, that&#x27;s game over.<p>You could encapsulate SSL in SSL, so the first SSL layer is decrypted by your &quot;colleagues&quot; but the second one should just flow freely.<p>The problem here is that (A) SSL is defeated in your corporate network and (B) other protocols are probably blocked, to force you to use the proxy to reach Internet, so you&#x27;re stuck with SSL.<p>Disclaimer: We haven&#x27;t tried these scenarios (defeat SSL sniffing on a corporate network) because it&#x27;s not the main use of our product and actually, as long as it&#x27;s legal and ethical you should follow your employer&#x27;s rules, so bypassing your company&#x27;s security systems is not our business nor we condone it.<p>But it&#x27;s technically interesting.<p>We[1] do SSL tunnelling to create private networks; unfortunately we don&#x27;t offer Internet gateways so it&#x27;s not exactly a VPN tunnel. You could, however, install a proxy or a router inside your private network and use it to route your traffic to Internet through the private network.<p>[1] <a href="https:&#x2F;&#x2F;wormhole.network" rel="nofollow">https:&#x2F;&#x2F;wormhole.network</a>