If you can't find the domains that the application is using, take a policy trace with all other apps closed on a client computer, and see what domains are being requested. If this is the route you choose, create a rule to disable a service based on the domains AnyDesk uses. Second, if you can't work out the incompatibility, bypassing a task (like authentication) is better than doing a full bypass. First, get a test user, and use the CPL Troubleshooting code (sometimes called the 'Magic Code' by our Support), and eliminate services one by one to see if the traffic handling improves. There is not a lot of info specific to AnyDesk and the ProxySG, and so I would do a couple things. If you do a full bypass, you create a blind spot for monitoring traffic. Also, for in order for traffic to show in the ProxySG Access Logs, it has to have been evaluated by policy. From a security standpoint, it is better to try and find out what that is, and to remediate it, or bypass it from the least amount of services as possible. Typically, however, usually there is some aspect that an application doesn't like, be it SSL decryption, authentication, or something else. If you want to bypass it from all ProxySG policy evaluation, you will need to reach out to Anydesk to find out there IPs, and use them to bypass like you have done in your case with Webex. I guess it really depends on what you want to bypass the application from.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |