I hope that someone can help us out with a bit mor insight in the URLF features of Endpoint Security. We installed the policy as mentioned in sk112932, and it is indeed blocking the forbidden sites. However, it seems to fail on certain sites, i.e *.google.de is allowed and also passed without a problem when within the network, but on the client it's blocked whereas *.google.com is passed as required. Other sites, mainly ssl ones are also blocked on the endpoint despite being allowed in the policy. Could anyone shed some light on how hte URLF works on the client and on which point in the stack it's blocking? I would've expected to be on application layer and so seeing the actual URL, but it seems it's blocking further down the stack and not being able to see it properly but only the certificate.
We're allowing split tunneling so the client isn't going through the gateway when connected to the VPN, just in case that's important.