Katie is a SOC analyst at an international financial corporation. Her team needs functionality so the system continuously scans logs for anomalies, identifies suspicious activities, notifies…

Question

Options

• ALog collection
• BAlerting and reporting
• CLog normalization
• DLog parsing

• A
  2% (1)
• B
  90% (44)
• C
  6% (3)
• D
  2% (1)

Explanation

Alerting and reporting is the SIEM/SOC function that turns detected conditions into actionable notifications and tracked incidents. The scenario requires real-time detection triggers (thresholds/anomalies), analyst notifications, and automatic ticket/incident generation with relevant context fields (event type, duration, affected device, OS version). That is exactly what alerting does: it monitors rules, correlations, and analytics outputs and produces alerts/incidents; reporting provides structured summaries and operational views for stakeholders and audits. Log collection is only ingesting data and does not create incidents. Log parsing extracts fields from raw messages, and log normalization standardizes those fields across sources-both are foundational, but they do not themselves generate alerts or tickets. In SOC practice, effective alerting depends on good parsing/normalization so alerts carry the right context, but the function that performs continuous monitoring and triggers incident workflows is alerting and reporting. This also supports escalation workflows, SLA tracking, and post-incident documentation because the alert/incident record becomes the primary case artifact.

No community discussion yet for this question.