Repository navigation
SOC CrowdStrike Falcon: one issue per process tree, not per detection - #1250
Closed
scottbrumley wants to merge 1 commit into
Closed
scottbrumley wants to merge 1 commit into
scottbrumley wants to merge 1 commit into
Conversation
Suppression keys on aggregate_id (CrowdStrike's process-tree grouping) instead of composite_id (one detection), still for 1 hour. A Turla Carbon replay drops from 130 issues to 46, all in the same case as before. Bursts of ~120 issues into one case leave about half of them never started by the playbook engine; fewer issues per attack keeps the queue clear. The first detection in a tree sets that issue's severity; later detections in the tree within the hour raise no issue of their own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VK24hKuKXVJfuVHg4Min9y
Contributor
Author
|
Closing: suppression loses later detections in a tree (a Low first detection would hide a later High one from the automation rule) and folds away techniques the assessment needs. Replacing with an aggregating rule: one issue per process tree carrying the highest severity and every technique. |
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.
What this changes
SOC CrowdStrike Falcon - Endpoint All Alertssuppresses onaggregate_id(CrowdStrike's process-tree grouping) instead ofcomposite_id(one detection), still for 1 hour. Rule, vendor contract (schemas/vendors/crowdstrike-falcon/falcon-detections.yaml), generated schema doc and both READMEs change together.Why
A CrowdStrike attack raises one issue per Falcon detection: a Turla Carbon replay gives ~120 issues in one case within minutes. On deathstar about half of such a burst never gets its playbook started (
runStatus: pending, playbookstate: new), and some finished runs stayrunning. Reproduced three times on 11–12 Nov (70/123, 78/123, and 53/106 even when paced at 20 events per 3 min); the same pattern goes back to September. Fewer issues per attack keeps the queue clear. The platform side is being raised with Product separately.Turla Carbon: 130 detections, 46 process trees.
Trade-off
The first detection in a tree raises the issue and sets its severity; later detections in the same tree within the hour raise no issue of their own. Their events stay in the dataset and in the case's investigation query.
Tested on deathstar
check_contributionpassed (upload retried once after a tenant 500).Replays need a run-unique
aggregate_idnow, or a rerun within the hour raises nothing:tools/replay_scenario.pyin #1251 and povkitinternal/replayin Palo-Cortex/povkit#33.🤖 Generated with Claude Code
https://claude.ai/code/session_01VK24hKuKXVJfuVHg4Min9y