Local LAN access (local as defined by the native/underlying IP subnet mask) is configurable on the Cisco IPSec and AnyConnect clients, but with GlobalProtect, it seems as though its built in as a 'feature', and no choice is available to the administrator (I'd really like to hear from PaloAlto tech guys on this - by design? undocumented?). Its a form of split-tunneling, allowing only local traffic (defined by subnet mask), and tunneling everything else. In the case of IP range overlap, or mistakes in local subnet masking, there can be some very interesting/annoying scenarios that crop up. I understand that local LAN access is often desirable by end users, particularly when wanting to print locally while 'in-tunnel'. The machine itself is no more or less vulnerable to attack (from the local LAN) when it is 'in-tunnel', except of course that it can potentially be leveraged to compromise the protected network in real time. There is little difference in my mind between a machine that can be compromised when it is not tunneled (assuming you are using the client on-demand) and one that can also be compromised while tunneled. A compromised system is a compromised system - the protected network is vulnerable in either case - just a matter of degrees. Windows (or other) firewall can/should be configured (by GPO in MS enterprise networks) to protect any machine that is going to spend any time on the 'dirty' Internet (hotels, airports, starbucks, home, etc), not allowing any connections TO the machine while 'offnet' (off the corporate network) - but I digress. In any event, the admin of the GlobalProtect gateway should be able to choose the operating mode they desire - this is a major shortcoming if there is not that level of control built into the GP client/server, and PA needs to speak to this issue. Have either of you opened a ticket on this?
... View more