I'm tightening up the web security at our business. I started by implementing Protocol filtering (regular and SSL) and web control.
I've moved on to add a squid proxy server (nothing to do with ESET) on our gateway and then blocking direct outbound access from the clients.
When I do this ESET's SSL filtering breaks SSL connections in Internet Explorer, interestingly Chrome still works.
If I allow direct access to the following addresses outbound through the firewall....
proxy-detection.eset.com
38.90.226.28
91.228.166.91
91.228.167.91
the SSL filtering works again. I found this out by monitoring the gateway firewall logs.
I suppose my question is.... is there any way to proxy these connections and/or shouldn't these checks be done by or through the local remote administration server?
I hope this makes some sense,
Cheers,
Dave.