cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

Correlation Rule - How to look for specific domain suffix

Jump to solution

Hello,

I'm looking for some assistance in creating a correlation rule that is able to look for a specific domain suffix like ".tor2web., .pw, etc" within the Domain or Web_Domain fields. I'd rather not dynamically generate a watch list then apply it to a correlation rule as its not very efficient.

Has anyone else been able to create a correlation rule by using a "contains" type operator?

Thanks,

Rob.

1 Solution

Accepted Solutions
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Correlation Rule - How to look for specific domain suffix

Jump to solution

Hi Rob,

I don't believe regex-based correlation parameters are permitted. Another way to accomplish this - aside from a watchlist, which does support regex, would be to adjust the parsing rule so that the TLD would be additionally parsed into its own field which could be indexed, manipulated and used for rules. Thanks.

Andy

View solution in original post

2 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Correlation Rule - How to look for specific domain suffix

Jump to solution

Hi Rob,

I don't believe regex-based correlation parameters are permitted. Another way to accomplish this - aside from a watchlist, which does support regex, would be to adjust the parsing rule so that the TLD would be additionally parsed into its own field which could be indexed, manipulated and used for rules. Thanks.

Andy

View solution in original post

Highlighted

Re: Correlation Rule - How to look for specific domain suffix

Jump to solution

Thanks for the response Andy.

For those interested in the technical details, I created two additional custom types (TLD1, TLD2) which I have indexed. I run a WebSense proxy and found the existing signature ID that parses the logs received (1018095), copied it and added the following regular expressions:

domain\x3d\x22[^\x22]+(\.[^\x22\d]+)\x22 - Maps to TLD1

domain\x3d\x22[^\x22]+(\.[\d\w][^\x22]+\.[^\x22\d]+)\x22 - Maps to TLD2

It's important to 'disable' the original 'Websense_Ent Websense SQL Event' rule (1018095).

I now have the ability to specifically chart 'suspicious' domains (.io, .pw, co.vu, .info, etc) as well as more effectively filter out known good sub-domains (.gstatic.com, .googleapis.com, .youtube.com, etc).

Hope this helps other people.

Cheers,

Rob.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community