02-01-2011 02:14 PM
I started researching why our users at a remote office (not connected via site-to-site link) were unable to print to their network printer even though the tick box for allow local LAN access on the Cisco VPN Client was checked off.
This brought me to the following document on the Cisco site:
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080702992.shtml
Having seen this feature enabled and working at much larger organizations I have some questions:
Looking to understand why this is not a good idea.
Solved! Go to Solution.
03-25-2011 02:20 PM
Nelson
Most of your question seems to derive from the assumption that Allow Local LAN Access is not a good thing. I would not necessarily agree with that assumption.
Clearly the default behavior is to not allow Local LAN Access. I believe that this is an appropriate default behavior since it puts the VPN client into the most secure position. But depending on the situation in your organization it may very well be a good thing to allow Local LAN Access.
I will suggest these points in response to the specific questions that you ask:
- Yes this is different from true split tunneling. I believe that the level of concern may not be zero, but it is a pretty small concern.
- while having a fully updated antivirus software does reduce the possibility of the PC being compromised it does not entirely eliminate that possibility.
- it is true that the PC could already be compromised/infected and would pose a threat. Allowing Loal LAN Access presents a very small increase in risk that the PC could be compromised while on line.
- there is a very small risk that a hacker could compromise some other device on the Local LAN and from that machine might compromise the PC with the VPN client while it was on line.
If your company is in an environment that requires a VERY high level of security implementation (perhaps Heath Care or Financial Services come to mind) then maybe you would be concerned about the risk involved in Allow Local LAN Access. For most of us the risk is negligible.
HTH
Rick
02-01-2011 04:05 PM
Hi Nelson,
Split tunnelling is a good idea or not depends upon the security needs of the organization, i am sure Financial/Medical organizations needs to take all steps they can to secure there edges.
Here's a good read on why split tunnelling is considered un secure :-
http://www.isaserver.org/tutorials/2004fixipsectunnel.html
Manish
03-25-2011 02:20 PM
Nelson
Most of your question seems to derive from the assumption that Allow Local LAN Access is not a good thing. I would not necessarily agree with that assumption.
Clearly the default behavior is to not allow Local LAN Access. I believe that this is an appropriate default behavior since it puts the VPN client into the most secure position. But depending on the situation in your organization it may very well be a good thing to allow Local LAN Access.
I will suggest these points in response to the specific questions that you ask:
- Yes this is different from true split tunneling. I believe that the level of concern may not be zero, but it is a pretty small concern.
- while having a fully updated antivirus software does reduce the possibility of the PC being compromised it does not entirely eliminate that possibility.
- it is true that the PC could already be compromised/infected and would pose a threat. Allowing Loal LAN Access presents a very small increase in risk that the PC could be compromised while on line.
- there is a very small risk that a hacker could compromise some other device on the Local LAN and from that machine might compromise the PC with the VPN client while it was on line.
If your company is in an environment that requires a VERY high level of security implementation (perhaps Heath Care or Financial Services come to mind) then maybe you would be concerned about the risk involved in Allow Local LAN Access. For most of us the risk is negligible.
HTH
Rick
03-25-2011 02:55 PM
Thank you Richard.
When I originally presented this idea to my senior network engineer at work he had a knee jerk reaction of no. This in turn led me to question some Cisco documents I had read and sparked a bit of research. I wanted to understand why would Cisco allow this solution if it was understood to create such a security concern. I also consulted with someone who is a senior network engineer and we came down to the same exact conclusion you had described in your reply.
I understand now that if the organization does not have to follow strict regulatory compliance guidelines then maybe we can trust the technology a bit more to do things like allow local lan access. We could always leverage a IDS/IPS solution if it security is still a major concern. While this is something I still cant implement at work, it will be something to definitely keep in mind for a future implementation.
Thanks again for your response!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide