Re: VPN Split-tunneling: Your opinion?
"Paul Melson" <[email protected]>
| Newsgroups | gmane.comp.security.firewalls.wizards |
|---|---|
| Message-ID | <001201c9f0e2$480c4a90$d824dfb0$@com> |
> I was wondering what each of your opinions are RE: VPN Split-tunneling. > Do you consider a split-tunnel setup to be particularly risky to allow from a security > point of view? Compared to typical (modern) exploits such as trojans via email, XSS, > web based attacks, etc - do you think that the risk of a client becoming misconfigured > and allowing routing into the private network via a split tunnel is particularly > prevalent? I think, for client VPN configurations, that split tunnel versus full tunnel setups are a dead horse. The original thinking was that you didn't want a computer to be simultaneously connected to a trusted network and an untrusted network. If those requirements are still part of your architecture, then do full tunnel. But in terms of actual risk, by having the client machine run with a host firewall that doesn't allow incoming connections (which is pretty standard fare for all vendors), you address the risk of someone bouncing through your clients from an untrusted network. Are there still attacks against VPN client systems that can get by a host firewall? Absolutely. However, full tunnel does little to nothing to prevent them. Most malware we see today does some form of phone-home from the client for C&C. If your full tunnel VPN configuration allows connected clients to access the Internet, that phone-home is still going to work (though centralized firewall & IPS will be in play). Even if your full tunnel setup prevents C&C, malware can still get on the client while it's disconnected and will gain access to your trusted network when the client connects. Having live C&C is not a necessity for theftware to pilfer data off of file shares or have a worm spread across the VPN tunnel. PaulM