docs(splunk): fix disposition join key to correlation_id::rule_id - #102
Merged
Conversation
Single-colon joins silently miss every closure. Matches disposition.py detection_key and the enterprise TA saved searches.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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
fleet-via-siem.mdfrom single colon to double colonWhy
disposition.pyusescorrelation_id::rule_idasdetection_key. A single-colon join silently misses every closure, so SOC searches never drop triaged findings.Matches enterprise TA saved search Untriaged critical or high in agentmetry-enterprise PR #9.
Test plan
docs/integrations/sigma/agentmetry_critical_detection_untriaged.ymlcomments