What is our primary use case?
Webroot is not just an anti-malware tool - it also offers a DNS security solution to protect against visiting malicious websites.
What is most valuable?
Webroot excels in DNS protection, particularly in blocking malicious sites and phishing. However, for advanced security needs in the evolving landscape of XDR, I prefer third-party specialists over solutions transitioning from traditional security products like anti-malware or DNS protection.
What needs improvement?
It addresses a specific risk related to malicious sites but doesn't cover broader security aspects. For the next release of Webroot, I would like to see features like sandboxing integrated into the DNS protection. In an XDR world, solutions like ESET and Cylance offer the ability to sandbox websites, allowing users to inspect them without the risk of malicious code. This would enhance flexibility and empower users to make informed choices. Additionally, refining pricing to align with the value of specific security or risk management needs would be beneficial.
What do I think about the stability of the solution?
Webroot has been stable, including Webroot DNS.
What do I think about the scalability of the solution?
In my limited experience with Webroot, it has shown good scalability, particularly in the enterprise context. When it comes to Webroot DNS, I find it to be a nice solution but prefer a more comprehensive approach. I lean towards XDR vendors that can integrate DNS protection into a unified dashboard, especially as traditional anti-malware solutions like Webroot face challenges with evolving threat actors. Currently, I have around 60,000 Webroot users for anti-malware, but for DNS protection, it is a fraction—about one or two percent—since some clients opt for other solutions. Traditional anti-malware technology is becoming less effective against sophisticated threats.
How are customer service and support?
Setting up Webroot is generally straightforward. Being part of OpenText, a large organization, their support is not bad, but it might not match the accessibility and immediacy of support from companies like Microsoft.
How was the initial setup?
In my experience, setting up agent-based XDR systems is more effective for device monitoring compared to relying solely on a Security Operations Center. While Microsoft has a lead, other vendors offer more comprehensive technology stacks to complement Microsoft's offerings. Anti-malware vendors like Webroot, Sophos, and Kaspersky may not be as dynamic as some other solutions in the current landscape.
What's my experience with pricing, setup cost, and licensing?
The pricing for Webroot DNS depends on the customer's specific needs and the value they place on protection. For general pricing, I would rate it around a six out of ten in terms of costliness. It is not overly expensive, but it is also not the cheapest.
Which other solutions did I evaluate?
In my view, traditional IT security vendors like Webroot, Sophos, and Kaspersky are facing challenges as their revenue is being eroded by newer players addressing advanced threats. While these traditional vendors are trying to adapt and enhance their toolsets, there are companies already built to effectively tackle the evolving threat landscape. The market is shifting towards those who embrace and understand these new challenges.
What other advice do I have?
From my perspective, the frequency of updates isn't a major concern as I don't handle integration or implementation. However, the challenge often lies in integration, especially when a product like Webroot has been acquired by a larger company, in this case, OpenText. For me, seamless integration with support desk systems, like Autotask, is crucial in making decision-making smoother.
Overall, I would rate Webroot DNS as an eight out of ten. For me to rate it a ten, seamless integration with ticketing and support desk systems is crucial. Automated problem resolution is key, and integration with support systems is a make-or-break factor.Webroot DNS is good at what it is built for—addressing malicious domain names. However, it is not at the top of my stack because I have other solutions that can handle this function. It is fit for its purpose, but it is not an all-encompassing solution like XDR or MDR.
