-
-
Notifications
You must be signed in to change notification settings - Fork 96
Introduce an experimental sigma
operator
#3138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2978989
to
7c63193
Compare
492d80c
to
7e7bcb5
Compare
b209f61
to
008ef36
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just leaving some notes for myself.
70e4ca5
to
1997e09
Compare
53ba52b
to
b51c1db
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I played around with this, managed to use this operator to continuously filter data, even while changing my rule file - and approved, considering that this is experimental.
I left some comments, probably for future consideration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing the issues!
I think this warrants an approval now, any more fixes afterwards seem to be superficial from here on.
7db3611
to
95a8c80
Compare
The
sigma
operator takes a path to a directory or a single *.yaml or *.yml file, takes all input events, and applies the sigma rule. The resulting events contain matches for the Sigma rule and the rule itself.