Separate Proxies & Translators category
The categories Proxies and Translators should be separate. Many customers would like to block sites categorized as proxies but allow sites categorized as translators. They should be configured like this by default.
Ex. translate.google.com is blocked by default.
Geochan joseph commented
OMG.. still same
Dave Palmer commented
We're rolling out Sophos. It's still early days, but this is already top of our list. I agree with below, would be useful if the 2 were separate categories. Pretty much the only thing we're doing at the moment is adding people to a group with a custom web policy which allows proxies and translators. We're close to allowing the category for everyone in the company, just to stop the requests coming in.
Im facing the same issue too. :(
Are you making fun of your customers? Looks like this category is itself a translation error !! "translator" would not it be sites that translate url? Because if not, what is the point of going to block sites that translate languages ???? And as usual with Sophos, total silence
Guys, it's 2019 and the proxies & translator is still a single category....shame on you!
Full agreement here, this combination doesn't make any sense in my opinion.
William Bain commented
I've just had to open access to all Proxies & Translators as users legitimately want to translate pages
Im fully agree
A non y mouse commented
I fully agree with this idea and even wonder why this is. As we're working in an international organization, we rely on translators heavily, however, using the proxy functionality of translate.google.com, all web-policies can be easily circumvented.