Skip to content

replay_scenario: run-unique CrowdStrike aggregate_id and composite_id - #1251

Merged
scottbrumley merged 1 commit into
mainfrom
tools/replay-crowdstrike-run-ids
Nov 12, 2026
Merged

scottbrumley merged 1 commit into
mainfrom
tools/replay-crowdstrike-run-ids

Conversation

@scottbrumley

@scottbrumley scottbrumley commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

What this changes

tools/replay_scenario.py gives CrowdStrike aggregate_id and composite_id a run-unique suffix, like the other vendors' ids already get. Detections in one process tree still share theirs within a run.

Why

The SOC CrowdStrike rule now suppresses on aggregate_id for an hour (#1250). The TSV ids are fixed, so without this a rerun within the hour raises no issues.

Tested

Normalizing two events from one tree gives both the same suffixed aggregate_id and distinct composite_ids; other vendors untouched. Used for the deathstar replays on #1250.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VK24hKuKXVJfuVHg4Min9y

The CrowdStrike rule suppresses on aggregate_id for an hour, and the TSV ids
are fixed, so a rerun within the hour raised no issues. Each run now gets its
own suffix; detections in one process tree still share theirs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VK24hKuKXVJfuVHg4Min9y
@scottbrumley
scottbrumley merged commit 0f219d3 into main Nov 12, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant