DNS Filtering Without Browser Extension
R
Ryan Kosowsky
It would be helpful to have DNS filtering without the browser extension. The agent already runs in the Windows kernel, and I feel has as much control as necessary to be able to filter at the OS level without the extension.
While I understand a lot of functionality of the software comes from the browser extension with things like browser isolation, credential protection, and download/upload protection, we may have deployments where we would prefer to filter with the agent rather than the extension. Especially with how incognito mode is treated, as easy as the instructions are when you install an agent on a new machine and it's very simple for the user to enable in incognito, some users are less tech savvy and are still going to just not read it and try to browse the web anyway, and it makes for a user experience that is not as good.
Log In
A
Andrew Barton
I'll add another scenario where this would be useful. We would like to be able to deploy the agent separately from the browser extension. During new client onboardings we often have issues caused by the browser extension interacting with other extensions or policies. It would be nice to be able to deploy the agent first to start collecting those logs and then schedule the browser extension at a different time (even when using "Monitor Only").
P
Patrick Murray
Agree. This would also resolve the compatibility issue with the Citrix Publish Apps and RDS RemoteApps scenarios.