ContentWatch in Salt Lake City, Utah offers ContentProtect, a web content filtering solution.
N/A
WatchGuard DNSWatchGO
Score 9.4 out of 10
N/A
WatchGuard DNSWatchGO provides DNS-level protection and content filtering that keeps the user's business safe from phishing, ransomware, and other attacks even when a user is outside of the network, without requiring a VPN.
If you are looking for something relatively inexpensive to lock down specific computers, it would be a useful tool. If the computers themselves aren't too locked down, implementation and management shouldn't be too difficult.
While DNSWatchgo offers the same categories as Application Control offers on the Watchguard firewalls, the WebBlocker categories are not offered. This is really a disappointment and Watchgurad should really consider adding the extra WebBlocker categories to DMSWatchGo. In my opinion, reporting in DNSWatchGo is minimal to say the least and could use drastic additions. as it is today it does offer very little info to the admins. The identification of registered clients is flawed. It seems that the same clients are registered multiple times on the management platform, thus unnecessarily consuming licenses. In my experience, it is really annoying to have to remove the duplicate clients every time again and again. On the positive side, when one already has Watchguard firewalls seting up DNSWatchGo is really easy, as it shares the same categories with Watchguard firewall Application Control. So easily one can almost the firewall functionality on laptops. And we say almost, because DNSWatchGo is missing the WebBlocker categories / blocking capabilities to be considered a full firewall replacement.
Our primary policy is a restricted list, so that does as advertised. We had one location that had blocks based on categories (adult, illegal, etc). We continually had issues with sites getting completely blocked due to unrelated content. For example, Yahoo had a beer ad on the page, alcohol was blocked, so Yahoo became blocked for the period of time that ad was displayed. We had this happen multiple times and eventually switched to a different solution at that location.
I've had issues with their cloud portal not working. I don't have to edit our configuration often, but on numerous occasions, i was unable to get the configuration page to load after login, sometimes for days. The platform just wasn't stable when I needed it to be.
We run many of our remote rooms as frozen (after logoff they reset to the image). This works fine most times, but when content protect needs a configuration change pushed down, someone needs to go 'thaw' the computers, download the updated configuration, and re-'freeze' the computer. It would be nice if that information was just dynamic from the cloud and didn't need to be pulled down.
The categorization used for policies is very limited and not flexible or easily customizable.
While DNSWatchgo offers the same categories as Application Control offers on the Watchguard firewalls, the WebBlocker categories are not offered.
Reporting is minimal and could use massive upgrades.
The identification of registered clients is flawed. It seems that the same clients are registered multiple times on the management platform, thus unnecessarily consuming licenses.
We really need an extra layer of protection for our laptops. Choosing the DNSWatchGo makes sense as we have Watchguard firewall. If we had another brand of firewalls we would probably use anther product instead!
At the time ContentProtect was selected, Forcepoint (Websense at the time) didn't have an inexpensive or cloud type product. The same can be said with Cisco, at that time. Recently, we have reevaluated and are going to be transitioning to Forcepoint's mobile client and removing ContentProtect from our environment. The cost is actually now less and we will be able to get both more dynamic control and also give us more detailed reporting on the traffic from clients.
At the time we were looking for a DNS based protection solution we had also tried "Blue Shield Umbrella". Both programs had similar behavior, but the main reason we eventually decided to go with DNSWatchGo was the fact the we have WatchGurd firewalls. So deploying DNSWatchGo was easy as we just copied the Application Control settings from our firewalls to the DNSWatchGo setup. Also Watchguard firewalls already have the DNSWatch service for the PCs that are connected to them while inside the company network, so it makes sense to equip them with the same shield while outside the company network.
It was a relatively inexpensive and simple solution when we needed one relatively quickly, which is a positive. The inexpensive price has kept it in the environment.
The lack of reliable reporting has lead to the need for an alternate monitoring solution in a few cases. Network level reporting was used, which is a separate expense, configuration.
Time has been lost waiting on the portal and then troubleshooting support tickets when sites that shouldn't have been blocked have been blocked. It has resulted in changes for locations that needed dynamic category filtering as opposed to a finite list.
The blocking of sites based on add traffic or sub-sites (rather than just blocking that content like other solutions) has resulted in downtime during classes when those sites were listed in the lesson plan and had previously worked.
