Our company is based in Sacramento. This solution is generally used for enforcing HR policy for enterprise. In our case, most of the clients are state government institutions. Palo Alto ensures that no hate speech or anarchy websites, for example, get through. We also implement this product. If somebody takes our recommendation and buys the product, they can trust that it's good because we're not partners with Palo Alto, we're recommending it because it's a good product. I trust PAN.

We have a few servers in DMC that are not going to go through proxy, but at the same time, they are trying to connect to the internet to download some updates from repo. So, anything that is not a red-hat-related repo or Apache-related repo is blocked, and we have a specific repository. This is when we have been trying to use a URL filter.

My primary use case is to ensure there's no need for a separate IDS or IPS solution.

We require a firewall to deploy URL filtering or to enforce this URL filtering solution to our users. It is actually cloud-based, deployed on a cloud, and is URL Filtering as a service, which requires a firewall. The firewall, therefore, will then enforce the URL filtering options on my users' traffic.

We are using this for preventing the user's access to malicious websites, or access to inappropriate adult websites or porn websites or even the P2P tunnels or tunnels or domains they should not access. This is our main priority and main use case.

We are not using it for the general population, just for a select group of users in an isolated subnet. We are using it primarily as a whitelist with little reliance on the PAN-DB.

Our primary use case of this solution is for both internal and external firewalls.

We operate in the automotive industry. Internally we work with computing and networking equipment, concentrated on collecting, storing, processing, and distributing enormous amounts of data. Our company deploys this solution for internal web security purposes.