When reviewing incident scoring in XSIAM, an analyst observes that multiple low-severity alerts have aggregated into a single high-severity incident. Which component of XSIAM is primarily responsible for grouping and scoring these related alerts into an incident?
Trap 1: The Parser Normalization Engine
Parsers normalize log formats into the XDM schema, not group incidents.
Trap 2: The Threat Intelligence Feed Manager
Threat intelligence provides IOC matches, not incident aggregation.
Trap 3: The XQL Query Builder
XQL is a query language used for ad-hoc searching and data exploration.
- A
The Parser Normalization Engine
Why it fails: Parsers normalize log formats into the XDM schema, not group incidents.
- B
The Threat Intelligence Feed Manager
Why it fails: Threat intelligence provides IOC matches, not incident aggregation.
- C
The Incident Stitching and Scoring Engine
The Incident Stitching and Scoring Engine correlates related alerts, grouping them into one incident and recalculating severity from the combined evidence. This directly satisfies the stem's constraint: multiple low-severity alerts aggregating into a single high-severity incident, rather than being scored independently.
- D
The XQL Query Builder
Why it fails: XQL is a query language used for ad-hoc searching and data exploration.