Not necessarily disagreeing, but without real world testing / comparisons to other products, its tough to say how "bad" or "good" they are.
We will have to see how long it takes Webroot to fix this. The cost of moving to another AV platform isn't quite worth it yet. We at least have visibility into these conditions and can work around them for now. This isn't a total deal breaker for us, but it isn't great. (Now that I know what to look for.) I had been wondering why we were getting alerts for infections when the dashboard showed nothing. Luckily our RMM tool monitors the "infection" registry key, so we have visibility into this.
If you are depending solely on the my secure anywhere site to report your infections, you are going to be missing a few. Access to the malicious file was blocked, but was unable to be cleaned. I have found malicious registry run keys as well as a malicious file housed in a server redirected folder in the local logs. It only logs the ones it can clean (or attempt to clean).Īll the infections are logged to the client's wrdata.log file though. The number one bug is that Webroot does not report all found infections to the secure anywhere dashboard.
WEBROOT DNS PRICING UPDATE
It's been escalated to development, but no ETA on when it will be fixed as it requires both a website and agent update to correct. Well, I've run into a few bugs that I think are rather major.
0 kommentar(er)
