Skip to content

Conversation

@rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

Reduce false positives in various rules by adding exceptions for process executables or file paths.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


Reduce false positives in various rules by adding
exceptions for process executables or file paths.
@rabbitstack rabbitstack added the rules Anything related to detection rules label Apr 29, 2025
@rabbitstack rabbitstack merged commit 4b411be into master Apr 30, 2025
18 of 23 checks passed
@rabbitstack rabbitstack deleted the rules-false-positive-tuning branch April 30, 2025 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rules Anything related to detection rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants