We primarily use this solution for filtering. It handles whitelisting and blacklisting URLs and websites that the client machines can go to.

We use the onsite DNS proxy running on a Hyper-V machine, and we use the WebTitan DNS servers for our forwarders.

The primary use case for WebTitan is content filtering, but we are also incorporating more security into that. For example, if we want to specifically block a web page or domain, we can do it through WebTitan. 

We use a SaaS version deployed globally throughout our offices. There are two ways to deploy WebTitan. One is a site-based deployment, and the other is an on-the-go or machine-to-machine deployment. We have all the sites deployed and are moving into an OTG configuration, so our laptops are protected. We are deploying OTG right now for all machines and DNS Proxy at all our locations.

We use the solution to monitor our computers, to filter out porn and whatever other content we decide. We can set it up as we wish, however, we have got it to monitor our computers for porn and malicious websites.

We use the solution for web filtering at our patient-access computers including a classroom for teens.

We have it set so that the majority of our users are highly restricted regarding the websites that they can visit. They're not even allowed to go to sites like Amazon.com or other sales sites or gambling sites. All of that is restricted. We have restrictions based on tiers, where our general population is restricted on what it can view online, and we have a "management" tier which it's much less restricted. And administrators, in IT, have wide-open access.

It is a SaaS solution but we have a proxy for it.

We use their cloud-base for the DNS, and this is called WebTitan. Basically, we send on a DNS request through their DNS servers for filtering. Our use case for WebTitan is to filter all the bad URLs to check and make sure that we don't have any malware, etc. that might go through our network. We use it to replace the traditional proxy that requires a server onsite with a CPU, etc. 

The main focus is just adding an additional layer of security to what we already have, knowing that no particular solution protects you 100%. It provides an additional layer of security while browsing the Internet, which seems to be the most vulnerable place for most companies. It doesn't necessarily mean you are going to a legitimate site, as it could be redirecting you to something malicious, which turns out to be pretty bad. We already have an existing antivirus and gateway security. This was more just an added layer. We are strictly using it as a DNS filter. It seems to achieve what we are looking for. It also blocks some content that could be potentially questionable or harmful.

For our main corporate LAN, we are using WebTitan DNS forwarders that we have set on our local LAN through their DNS filtering servers. Then, we use the OTG client for our mobile devices. We also have laptop users who may or may not always be at our main corporate LAN office, and when they are not on the premises, they use the OTG client.

We are strictly Windows-based.

We use it for the Child Protection Internet Act so that we can block things that kids shouldn't get into. We use it just for our computers that are here at the library.

It is a web filter. We use it to keep people from streaming in our main office. Everything goes through our main office, and we don't want it to be clogged so that nobody can get to it. We have to limit the streaming capabilities of the users and access to any inappropriate sites.

The way I use it is that I log into their portal and make changes to the filter. There isn't any hardware. Basically, it goes by DNS settings. So, the DNS server goes out to WebTitan and says, "Is this okay to go to?" If WebTitan says yes, they get their webpage. There is no hardware other than our DNS server that interacts with the service.

As a library, we are required to have a filter on our public computers because we receive E-Rate funding. If children use our computers, the usage has to be filtered. 

I set up the usage filters. There were items on that list that were not going to harm children, things like shopping for a used pickup truck. You can filter all of those things and I chose not to filter some. But the whole idea is to block usage so that patrons can't access pornography or any images that would be harmful to children.

We use it for all of our customer-facing desktop clients so that we can control and restrict access, versus using MAC address restrictions and the like. The roaming version is the one that we use most, versus at the firewall level.

We have a lot of employees that use common hardware but they log into each one. Because we have customers who need to be served quickly, we're not into a group policy situation, where we have too many policies or restrictions. We want the desktop clients to be something that employees can log into quickly, without going through security settings.

Our use case is about protecting our infrastructure. We also restrict certain user profiles, so as a productivity tool it blocks access for general browsing.

Our use case is that when we take laptops off-prem they will still have DNS filtering on. Regulators suggested that we needed something along these lines for when laptops go off-prem. That was the main driver.

We use it for DNS Web filtering.

We use this product to stop cyberattacks and make life easier for staff members concerned with breaches to the code of conduct.

Previously, we used Cisco Umbrella and suffered a cyberattack due to one of the websites that a member of staff had visited. The malware was placed on our systems and an exec almost provided access information to a well-known group of cyberattackers.

We are an MSP and we have customers that we need to protect with a web filter. We are doing a trial of WebTitan with one of our big customers.

We typically use the solution to filter web access. We don't connect to the internet with our workstations. They are behind the firewall and all the traffic goes through a proxy server in order to implement content filtering. With some users, we use this solution to restrict access to specific websites only.