Webroot SecureAnywhere and Mamutu?

There's a Behavior Shield in WSA. Is that a duplication of what the behavior blocker Mamutu is doing? Would you recommend turning off the Behavior Shield, uninstalling Mamutu, or running both together?

 

WSA is a behavior blocker per definition (+ many other things), so you have a clear overlap there. I have not seen reports of conflicts with it but may be better to find a better complementary security tool if you really need to run something else on top of WSA.

 

Okay, thanks fax, I'll uninstall Mamutu. Not sure if I'll replace it with anything, have to think about that.

 

I just got a PM about my WSA/Mamutu question:

"Webroot claimed to have 'tens of terabytise' of signature database in the cloud, so is far from being a behavior blocker."

The only other relevant thing he says is that I should keep Mamutu because it is a "profesional behavior blocker". Does this make sense? Is the WSA behavior blocker in the cloud? Is it not as strong as Mamutu?

 

You can use both if you like and see how it goes and report back. https://detail.webrootanywhere.com/agenthelp.asp?n=Changing_Behavior_shield_settings

TH

 

To the sender of the PM - I don't see how having a central database precludes it from being a behavior blocker? WSA uses the cloud to minimize prompts and intelligently respond automatically to behaviors. You can increase how many of these show to the user by increasing your heuristic settings, but it isn't necessary. We've designed WSA to specifically avoid the scenarios where users have to answer dozens of prompts because you shouldn't have to do so to be secure.

 

And for WSA a perfect example of where, default is best. Their default settings are right on the money. You really do not have to touch a thing.

 

Thanks for answering my implied question that wasn't asked clearly. I couldn't see why a BB couldn't be cloud-based if done right.

 

Good to know, trjam. I had a subscription to WSA Essentials that I didn't use much because it seemed they were still refining the software. After reading some reviews a few weeks ago I tried it again and really like it. Not sure if it's because WSA has improved in the last year or that I understand it better. Just upgraded to Complete and it's working fine right out of the box.

 

I think Mamutu and WSA could be used together. Unless you find a specific case of conflict I don't see any reason not to use them.

 

Finally took your suggestion Amit and am running WSA and Mamutu together without any problem so far.

 

using EAM full (mamutu BB inside) and WSA together. WSA leaves Mamutu doing the job (as he should do), and kicks-in if Mamutu does not react.