With TeamViewer, one thing you can do for your endpoints is deploy a customized host module to which you can then apply policies (like don't show the password on screen that an external party could use to connect, etc.). Sure not all firewalls are great in this role, but some are really doing a pretty good job. employees may access the mail server, while partners can not).īut when you want to control it, know from one central point, who was when connected and what resources he has accessed, than Teamviewer and SSH simply don't give you the same insight as you have on a modern firewall, acting as a VPN gateway. Also you wouldn't give access to the same resources to all of your VPN users, but limit them by users and groups (e.g. If you don't trust them for a VPN connection, than you probably wouldn't trust them for any other kind of remote connectivity as well. However, isn't that just a firewall issue? I've heard the argument against so many times I started wondering if there was some security vulnerability that I wasn't aware of.It depends who is 'them' - it is supposed to be a list of your own employees and certain trusted partners, you have allowed VPN access rights. The big argument I keep hearing that VPN exposes "you to them and them to you".
0 kommentar(er)
