What users are saying about
1 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 3 out of 100
3 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8 out of 100

Likelihood to Recommend

ContentProtect

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.
Anonymous | TrustRadius Reviewer

Webroot DNS Protection

DNS protections is necessary everywhere. There are options in the market place, but Webroot has it priced right and easy to implement into your MSP Platform.
Rob Morton | TrustRadius Reviewer

Pros

ContentProtect

  • The client is relatively light weight and doesn't impact other applications.
  • The client isn't easily bypassed, so the user's are kept under restrictions.
  • The configuration is relatively simple and easy to deploy.
Anonymous | TrustRadius Reviewer

Webroot DNS Protection

  • Policies by IP, Groups, and even by device.
  • Cloud based, no hardware.
  • Protects at the domain which helps support our at workstation level protection.
Rob Morton | TrustRadius Reviewer

Cons

ContentProtect

  • 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.
  • I could never get the usage reporting to work.
Anonymous | TrustRadius Reviewer

Webroot DNS Protection

  • Technology and SAAS platforms are always evolving.
  • Platform console ease of use.
Rob Morton | TrustRadius Reviewer

Alternatives Considered

ContentProtect

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.
Anonymous | TrustRadius Reviewer

Webroot DNS Protection

Webroot stacks right up with the top vendors in this tier. Priced right and MSP ready.
Rob Morton | TrustRadius Reviewer

Return on Investment

ContentProtect

  • 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.
Anonymous | TrustRadius Reviewer

Webroot DNS Protection

  • Network stability of our clients
  • Hard to prove ROI until you have had fallen victim to an attack that you were not prepared for.
Rob Morton | TrustRadius Reviewer

Pricing Details

ContentProtect

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Webroot DNS Protection

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison