Webroot is Your Roadrunner to Other Antiviruses' Coyotes
April 04, 2017

Webroot is Your Roadrunner to Other Antiviruses' Coyotes

Chris Skurkey | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Webroot

It is used across the whole network. It is pushed out to all users by the domain controller. It is what we use to protect all of our machines and computers.
  • Great protection.
  • Easy to deploy.
  • Easy to manage by all users. If they have a blocked email, each user can log into a portal and find out why, and let it through based on their understanding of the nature of the email.
  • If there is no network connection to the cloud infrastructure, there will be no protection (drawback if there is no "layer 1" connection).
  • Heuristics can only combat some viruses, so it probably needs more methods to combat different viruses.
  • There are some instances where the server fails to push out (the server's fault), leaving a small fraction of users unprotected when they are set up for the first time.
  • There are no legal problems to hurdle, because it shows quite well how committed we are to preventing information loss.
  • It also shows how committed to protecting data - such as HIPAA concerns.
  • Using it is a demonstrate how to properly display a companies priorities when it comes to spending the right amount of money on a very reliable service. "We are not cutting corners" is the message there.
Symantec.cloud, Sophos, McAfee (which was terrible, and we had to replace McAfee with Symantec.cloud at another company). However, the difference between Symantec.cloud and Webroot is primarily with notifications and installations of definition updates. There was a lot more intervention with Symantec, especially when it came to uninstalling Symantec clients - which was a hell in and of itself. I've also used Trend Micro, MalwareBytes and other AV tools over the years. You just don't notice Webroot when it is running and doing its job.
Webroot is not a CPU hog, so it doesn't slow down the performance of our end-users' machines. Updates don't interfere, also, and there is no "walking on eggshells" when it comes to matriculating those updates. There is no need for such gentle handling. The same goes for definition updates also. Even when the risk of infecting a machine when the network is not connected, or when a USB drive is inserted while offline - those incidents are the times we tell our end-users to be careful when they do NOT have an internet connection.