-
Notifications
You must be signed in to change notification settings - Fork 513
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
[Rule Tuning] Windows BBR Tuning - 1 #3380
Conversation
@@ -37,7 +37,7 @@ timestamp_override = "event.ingested" | |||
type = "eql" | |||
|
|||
query = ''' | |||
file where event.type in ("creation", "change") and | |||
file where event.type in ("creation", "change") and process.executable != null and not user.id : "S-1-5-18" and |
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 don't think we should tune this rule. The intent is to identify any file that is compressed without depending on the file extension. It should be used as contextual, which is why it is a BBR. Its need was based on identified gaps of other detection methods for compression which were more brittle
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.
The problem is matching on system functionality instead of user behaviors, like the firefox one represents 20% of the volume (2M alerts if I remember correctly), just related to cache files and other browser-related stuff
@@ -35,13 +35,16 @@ file where host.os.type == "windows" and event.type == "creation" and | |||
|
|||
( | |||
( | |||
process.name : "System" or |
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.
should we be tuning this one either, based on description?
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 think any rule can use some tuning to exclude common system activities
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
* [Rule Tuning] Windows BBR Tuning - 1 * . --------- Co-authored-by: Samirbous <[email protected]> (cherry picked from commit 8274f9a)
Issues
Part of #3186
Summary
Tunes the following rules:
Promotes the following to normal DRs: