Some SharePoint sites are accessible, while others are not. It is possible that some URLs have been redirected. To check this, we need to check the Symantec database to determine if there is any confidential, educational, or financial information or if there are any symptoms of threats such as ransomware like RED. Based on this, we need to reclassify the URL. If it is reclassified, we can allow that particular URL into the environment.

We use the product for malware filtering, content filtering, and reporting.

I have deployed the solution on three of the major cloud providers, GCP, Amazon AWS, and Microsoft Azure.

We use the policies of Symantec Proxy, particularly firewalls, ATP, isolation, and sandboxing, which are available in both cloud and on-premise deployments of the solution.

The solution is a proxy for our users to get onto the internet, and it does actually work. It does block users if they don't have access to those URLs. It's just that it's a very cumbersome solution and there's no real authentication to the user before the user tries to get out onto the internet. So there are quite a few problems with WSS, hence our reason to switch over to something different.

The solution helps with content monitoring, authentication, and cache. 

For use cases, I have created an integration with Active Directory for authentication and privilege-based access control. It enables us to manage bandwidth for users based on their privilege levels. For example, if a user wants to use a certain application or resource, we can provide access based on their privileges.

Our second use case was to ensure that the corporate network is only accessible by authorized users to prevent unauthorized access to private emails and other confidential information. It was a domain-wide access use case.

Our third use case was to block unwanted and malicious websites. We tried to achieve this through integration with other security solutions, but it was not successful. Also, we faced an issue with Cislope forwarding, as it is not supported in Symantec Proxy. Therefore, we used a reporter server to forward the Cislope to the C.S.I.M. system.

We are using Symantec Proxy for outbound traffic URL filtering, and antivirus scanning of whatever package is going through the proxy system. It's fulfilling all our requirements.

What we did is we replaced the TMG from Blue Coat, and we deployed the cloud solution to have URL filtering through cloud. When a user starts to work from home, they shift towards the cloud. Whenever they come to the office, they use the Proxy, on-prem solution. It's to secure their users and restrict them within the company policies to ensure they use specific websites or URL categories.

We are resellers and we implement this solution for our clients.

We use it for browsing and for updates to our system. We use it for remote access and for meetings as well now.

We are resellers and we provide solutions to our customers.

We use Symantec Proxy for a forward proxy.

We use Symantec Proxy to provide users with internet access, to allow the service to receive updates from the internet, and to block malicious websites.

We are an integrator and we have configured Symantec Proxy to be used in a bank as a proxy.

We use it for web security and content filtering. We are using Symantec ProxySG.