Skip to content
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

Merged
merged 4 commits into from
Feb 5, 2024
Merged

[Rule Tuning] Windows BBR Tuning - 1 #3380

merged 4 commits into from
Feb 5, 2024

Conversation

w0rk3r
Copy link
Contributor

@w0rk3r w0rk3r commented Jan 10, 2024

Issues

Part of #3186

Summary

Tunes the following rules:

  • File Compressed or Archived into Common Format (Excludes some high volume processes as a first step, still a noisy rule in general)
  • Potential Credential Access via Memory Dump File Creation
  • Attempted Private Key Access

Promotes the following to normal DRs:

  • PowerShell Script with Webcam Video Capture Capabilities (0 hits last 90d, non-noisy)
  • Kirbi File Creation (TPs only)

@w0rk3r w0rk3r added Rule: Tuning tweaking or tuning an existing rule OS: Windows windows related rules Domain: Endpoint backport: auto bbr Building Block Rules labels Jan 10, 2024
@w0rk3r w0rk3r self-assigned this Jan 10, 2024
@@ -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
Copy link
Contributor

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

Copy link
Contributor Author

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
Copy link
Contributor

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?

Copy link
Contributor Author

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

@w0rk3r w0rk3r merged commit 8274f9a into main Feb 5, 2024
13 checks passed
@w0rk3r w0rk3r deleted the rt_bbr_1 branch February 5, 2024 15:47
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
protectionsmachine pushed a commit that referenced this pull request Feb 5, 2024
* [Rule Tuning] Windows BBR Tuning - 1

* .

---------

Co-authored-by: Samirbous <[email protected]>

(cherry picked from commit 8274f9a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport: auto bbr Building Block Rules Domain: Endpoint OS: Windows windows related rules Rule: Tuning tweaking or tuning an existing rule
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants