What is a SIEM?
A SIEM collects security logs from across an organization, stores and searches them, and runs detections so a SOC can find and investigate threats.
Definition
SIEM
Also called Security information and event management
A SIEM (security information and event management) system collects security logs from across an organization, stores them in one searchable place, and runs detection rules over them so a security team can find, investigate, and respond to threats.
How it works
NIST's log management guide describes SIEM software as centralized logging software. Its log servers analyze events, its database servers store them, and it collects from the systems that generate logs either through agents installed on those hosts or agentlessly, by pulling from or receiving data sent by them. A modern SIEM takes in endpoint telemetry, identity provider sign-ins, cloud control-plane audit logs, SaaS activity, and network data. It parses each event into fields (log normalization), stores the result, and makes it searchable in a query language such as Splunk's SPL or Microsoft Sentinel's KQL.
On top of storage sit detections: scheduled searches or streaming rules that match known-bad patterns, correlate events across sources, or flag deviations from a baseline. A match becomes an alert, which an analyst or an automated workflow triages.
Example
An attacker with a stolen password floods a user with MFA push requests, hoping they'll approve one. The identity provider logs each denied push. A SIEM detection counts denials per user over a short window and raises an alert when a user crosses a threshold. The analyst then searches the same SIEM for that user's recent sign-ins, new device enrollments, and source IP addresses to decide whether the account is compromised.
Why it matters for a SOC
The SIEM is where most detections run and where investigations find their evidence, so what it can see bounds what the SOC can catch. NIST notes that SIEM software is usually more complicated and expensive to deploy than centralized syslog. Pricing that grows with ingest volume pushes teams to leave log sources out, and every source left out is a blind spot for detection.
Newer designs loosen that constraint. Cotool's SIEM, for example, writes detections in Python rather than a proprietary query language, can search and detect on sources it doesn't ingest by querying them where they live, and sends every alert to an AI agent for investigation.
Related terms
- Log normalizationLog normalization is the process of converting each field in log data from many different sources into a consistent name, format, and data type, so events can be searched, correlated, and analyzed together.
- UEBAUEBA (user and entity behavior analytics) is a detection technique that builds a baseline of normal activity for each user, host, application, and other entity, then flags behavior that deviates from that baseline as a possible threat.
- XDRXDR (extended detection and response) is a security platform that collects and correlates threat data from endpoints, identities, email, cloud workloads, and networks so analysts can detect, investigate, and respond to attacks that cross those domains.
- Security operations centerA security operations center (SOC) is the team, processes, and technology an organization uses to continuously monitor its systems and to detect, investigate, and respond to cybersecurity threats.
Go deeper
- Legacy SIEM vs modern SIEM: what changed and how to chooseLegacy SIEM vs modern SIEM: where logs live, how detections are written, what happens after an alert fires, and what each costs, with real product examples.
- What is SOAR, and is it still worth buying?SOAR (security orchestration, automation, and response) connects security tools and runs playbooks on alerts. How it works, the main products, and where playbooks break.
- What security log data should you store, and where?Store identity, EDR, cloud control plane, DNS, VPN, and SaaS audit logs where detections can read them fast; query the rest in place. Retention rules included.
FAQ
- What is the difference between a SIEM and log management?
- Log management collects and stores logs. A SIEM adds security analysis on top: parsing logs into fields, correlating events across sources, running detection rules, and raising alerts that analysts investigate.
- Is a SIEM the same as SOAR?
- No. A SIEM detects threats in log data and raises alerts. SOAR automates what happens after an alert, such as enrichment, ticketing, and containment steps. Many platforms now bundle both.
Sources
- Security Information and Event Management - Glossary | CSRC · accessed November 16, 2026
- NIST SP 800-92: Guide to Computer Security Log Management · accessed November 16, 2026
- What Is SIEM? | Microsoft Security · accessed November 16, 2026
- AI-Native SIEM Built for Agents | Cotool · accessed November 16, 2026
