[New] SIEM Rule Tuning - #27
Open
Mikaayenson wants to merge 1 commit into
Open
Conversation
Add example workflow that uses ES|QL alert history and Agent Builder to tune noisy SIEM detection rules.
This file contains hidden or 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
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.
Summary
Example workflow for tuning a noisy SIEM detection rule on Elastic Security.
Uses 7-day alert history from
.alerts-security.alerts-*. ES|QL checks alert volume and spread; if the rule looks noisy, Agent Builder agentsiem-rule-tuningreviews the rule and top alert patterns and suggests a query edit or rule exception. Setapply_changes=trueto PATCH the query or add an exception via the Detection Engine API.Manual test target: RDP (Remote Desktop Protocol) from the Internet. Requires 9.5+, Workflows, and Agent Builder. Agent instructions in
siem-rule-tuning-agent.md.rule_idfrom manual input or the triggering alerttuning_preference:auto,query_change, orexceptionapply_changes: recommend only or applyQueryTuning.mov
RuleException.mov