matching: multi match support #331
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds support to specify multiple conditions to match a rule. Syntax: multi:<match_condition1>;<match_condition2>;...<match_conditionN>; Examples: Match all rules including the term "nmap" but just from the "emerging-scan.rules" file. multi:filename:rule/emerging-scan.rules; re:nmap; Match all rules with a recent cve reference and a perimeter deployment multi:re:cve-202[23];metadata: deployment perimeter; Ticket: #2509
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make sure these boxes are signed before submitting your Pull Request
-- thank you.
https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Contributing
contribution agreement at
https://suricata-ids.org/about/contribution-agreement/
changes made (if applicable)
This is an implementation of redmine 2509
Describe changes:
This is a resubmit of pr #37. After reworking to fit the 2023 code base.
It adds support to specify multiple conditions to match a rule.
Syntax:
multi:<match_condition1>;<match_condition2>;...<match_conditionN>;Examples:
Match all rules including the term "nmap" but just from the "emerging-scan.rules" file.
multi:filename:rule/emerging-scan.rules; re:nmap;Match all rules with a recent cve reference and a perimeter deployment
multi:re:cve-202[23];metadata: deployment perimeter;