SOC operations

SIEM Fundamentals

Overview

A SIEM collects, stores, searches, correlates, and analyzes security logs from across an entire environment — the primary tool SOC analysts work from day to day.

Key concepts

  • Log ingestion, normalization, parsing
  • Correlation, detection rules, queries
  • Common log sources: Windows, Linux, firewall, DNS, cloud, identity

How it works

A SIEM (Security Information and Event Management system) collects, stores, searches, correlates, and analyzes security logs from multiple sources.

Core SIEM terms

TermMeaning
LogA recorded event generated by a device, system, application, or security tool.
Log sourceA device, service, application, or platform that sends logs to a SIEM.
Log ingestionThe process of collecting and sending logs into a SIEM.
Log retentionHow long logs are stored before being deleted or archived.
NormalizationConverting logs from different sources into a consistent format so they can be searched together.
ParsingExtracting useful fields — usernames, IPs, timestamps, event IDs, filenames — from raw log data.
CorrelationCombining related events from multiple sources to identify suspicious patterns.
Detection ruleA logical condition that generates an alert when specific suspicious behavior occurs.
QueryA request used to search, filter, or analyze log data — the same concept used to pull data from any database.
Data source coverageThe amount and quality of security visibility provided by the logs feeding a SIEM.

Common SIEM log sources

SourceWhat it captures
Windows Event LogsAuthentication events, process creation, account changes, security-policy changes.
Linux logsAuthentication activity, system events, service activity, command execution.
Firewall logsNetwork traffic allowed, blocked, or inspected.
DNS logsDomain-name requests made by devices and users.
Proxy logsWeb requests passing through a proxy or secure web gateway.
VPN logsRemote-access connections, authentication attempts, device info, session activity.
EDR logsEndpoint telemetry — processes, command lines, file changes, network connections, alerts.
Email security logsPhishing attempts, malicious attachments, blocked messages, spam, delivery activity.
Cloud logsAccount logins, administrative actions, file access, configuration changes, API activity.
Identity-provider logsAuthentication and account-management records from Active Directory, Entra ID, or SSO platforms.