For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content
Cortex XDR

Case lifecycle and grouping

Understand Cortex XDR case grouping and lifecycle stages, from signal investigation through resolution.

From signals to cases

  1. Ingest and stitch: Data from endpoints, firewalls, identity providers, and cloud sources is normalized, and related activity is stitched into causality chains. See What is Causality?.

  2. Detect: Detections raise issues.

  3. Group: Related issues are grouped into a case using shared artifacts, matching attributes, or related entities. If there's no match, a new case is created. See Case grouping.

Lifecycle

Stage
What happens

New

A case is created from grouped issues and enriched with threat intelligence and asset context.

Triage

Severity and scoring help prioritize. Playbooks can run automatically.

Investigate and contain

Analysts review the timeline, causality, and evidence, and take response actions, manually or through playbooks.

Resolve

The case is closed with a resolution reason, manually or automatically.

History and knowledge retention

  • Search past cases and issues to find similar activity, and use playbooks to compare a new case with previous verdicts.

  • The case War Room and timeline keep the full record of actions, notes, and evidence. Retention follows the default retention period for cases and issues.

Reporting

Issue and case notifications can be forwarded by email, Slack, syslog, and other destinations, and synchronized with ticketing systems through Marketplace integrations. You can also schedule reports from dashboards.

Last updated

Was this helpful?