On Thu, 29 Dec 2005, Pete Verdon wrote:
> I'm not an expert on VPN, but as I understand it if you're using a
> VPN then for most purposes it's as if your computer was plugged in
> in a machine room at the office. Any company policies about what Web
> sites you can look at and what other services like Usenet or native
> (non-hotmail) email you can use will then apply, whether through
> "paper" rules or technical restrictions. Whether this is a problem
> for you depends on the company.
When using VPN, you have, logically, two different network interfaces:
your native ISP interface with its ISP-provided IP address, and your
VPN tunnel with its VPN-provided IP address.
Potentially, this could be a security compromise: steps have to be
taken to prevent traffic from the hostile Internet from being routed
into the VPN tunnel and thus into the company's network, thus
bypassing the corporate firewall.
It may be that some VPNs enforce this by disabiling native access to
the ISP's network. From what I've heard of our own campus VPN (I
don't use it myself), it doesn't go that far, although it does take
certain precautions to avoid the VPN client leaking in such a way.
Additionally, it won't enable the VPN unless the antivirus
installation checks-out as working and up to date.
AFAIK, users who have enabled this VPN are still free to browse the
rest of the web, for example, directly via their ISP. Only the
traffic that is specifically destined to/from the VPN goes by that
particular route. But, as I say, other VPNs might apply different
rules.
h t h
|