Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our IT department uses TeamViewer to provide support to users at remote locations. More recently we've noticed that users are using TeamViewer to get support for their lab equipment from vendors.

Though I support the idea, it does bug me a little bit that someone could either accidentally or maliciously leave a session open, even though they're no local administrator, and thus create a hole in the firewall. In other words, this seems like a mayor security issue to me.

So my question is how do other organizations handle these type of tunneling applications (e.g. TeamViewer, WebEx, GoToMeeting, and TOR)? And has anyone suggestions as how one can regulate/govern these applications and still continue to use it for proper scenario's?

share|improve this question

The most common solution I see is to have the firewalls at each location set up to only allow the tunnel to connect to specified endpoints. This means it can still be used for the purposes intended, but can't be used to access other locations.

A pre-requisite is that you maintain centralised control over firewalls and endpoints, so there is no way to avoid access control.

share|improve this answer
I agree that your answer would work with most software. However, we use a firewall solution which doesn't allow easy on-the-fly ACL adjustments. Second problem is that the tunneling software mentioned tunnels over HTTP, which makes it even more difficult to limit connectivity to certain endpoints; the firewall doesn't have any notable proxy capabilty. – SilverViper Oct 6 '11 at 0:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.