Hey everyone,
I've been trying to find the best ways to ensure that TeamViewer QuickSupport (QS) is as secure as possible for my users, despite its known vulnerabilities. Currently, I'm deploying TeamViewer QS via an app-v package alongside Remote Desktop Services (RDS) and Internet Web Client (IWC), which has been working well. I also created a script to clean up the temporary files that are generated when launching the app.
My security team wants the connection ID to be randomized, but I've found conflicting information online. Some sources say it's possible, and others say it's not.
So my main question is: what strategies do you all use to enhance the security of TeamViewer or TeamViewer QS?
4 Answers
Honestly, the best security measure would be to avoid using QS at all. Instead, opt for the TeamViewer Host version with the password disabled and enable Easy Access. Also, implement Conditional Access in your Identity Provider to manage login restrictions. To further secure connections, restrict permissions and connection times through TeamViewer's settings, and block any outbound TeamViewer traffic on your firewall to only allow connections through your private router. This way, you can leverage all the features without compromising on security.
If you want to keep using TeamViewer QS, try isolating it as much as possible. Run it in controlled environments like RDS, just like you're doing right now. Make sure to restrict outbound connections solely to TeamViewer endpoints and enforce short-lived sessions. This way, you can monitor usage centrally. Ideally, if your organization already has a built-in remote access system like VPN or RDP, push for that instead of using TeamViewer unless absolutely necessary.
You might want to consider whether TeamViewer is the only option. If it's just for screen sharing, there are plenty of other tools out there that are more secure and less shady than TeamViewer. Just something to think about!
As for your security team wanting to randomize the connection ID, I'm really confused about the logic behind that. It doesn’t seem to be directly related to actual security. Instead, focus on blocking any TeamViewer-related applications by their developer certificates using your company's security tools, like XDR or AppLocker. This will provide a more effective solution.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures