Jump to content

Rules.Ref Contents Question

Recommended Posts

I am going to ask a question that I hope is not off-limits. If it is, I apologize, in advance.

In general terms, what is in Rules.Ref? I am not interested in "cracking open the file", I have no interest in reverse engineering it, just what types of information is in the file. Does MBAM use definitions of bad code in the same way as AV programs typically do? Or is it a list of the bad IP addresses that get blocked? I guess the most important point is this: how does MBAM usually protect from the baddies more quickly than the other products out there. SAS, for example, excuses their inability to stop the System Tools fake alert due to it's polymorphic behavior, constantly changing, so they are always in catch up mode. Does MBAM act (and react) the same way?

Or does it use more behavior analysis to figure out bad behavior?

Randy C

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.