Question

Difficulty: MediumLog Analysis and SIEM Management

A security engineer is configuring a newly deployed Security Information and Event Management (SIEM) system to ingest and analyze multi-source telemetry across the enterprise network. Arrange the core stages of the SIEM log processing pipeline in the correct sequential order from initial intake to operational notice.

  1. 1Log Collection
  2. 2Parsing
  3. 3Normalization
  4. 4Correlation
  5. 5Alerting

Answer

The correct order of stages in the SIEM log processing pipeline is: Log Collection, Parsing, Normalization, Correlation, and Alerting.
The SIEM log processing pipeline must ingest raw logs before evaluating them. Log Collection receives raw telemetry from source hosts. Next, Parsing extracts discrete fields from unformatted text strings. Once parsed, Normalization maps those fields into a uniform taxonomy so events from different vendors can be understood under a single schema. Correlation then evaluates these normalized events across time windows and sources against threat rules. Finally, Alerting notifies security analysts when rule conditions are satisfied.

Step-by-Step Solution

1
Identify the initial intake phase of event data
Log Collection gathers raw telemetry from endpoints, network devices, and security controls.
Before any processing can begin, raw logs must be collected from their original sources.
2
Structure the unformatted log text into defined fields
Parsing breaks down raw strings into structured data elements like IP addresses, timestamps, and action codes.
SIEM systems cannot efficiently search or evaluate unstructured text without extracting key attributes.
3
Standardize variable field naming across disparate vendor formats
Normalization converts heterogeneous fields (e.g., 'src_ip' vs 'source_address') into a single common schema.
Correlation rules require uniform field names to effectively compare events from different vendors.
4
Evaluate uniform log data against security logic and threat indicators
Correlation cross-examines normalized events to identify suspicious patterns and multi-host activity.
Rule matching must operate on standardized, parsed telemetry to produce reliable threat detection.
5
Notify analysts or triggering automated incident response mechanisms
Alerting dispatches high-priority tickets or push notices for identified threats.
Alerting occurs only after correlation engines determine that specific event thresholds or rules have been triggered.

Key Concept

SIEM Log Processing Pipeline
Rate this question