Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is SIEM?

SIEM (security information and event management) is technology that collects, correlates, and analyses log data from across an organisation to detect threats and support investigations.

Illustration for the cybersecurity term SIEM
Home / Blog / Cybersecurity Terms / What Is SIEM?
17 November 2026

What Is SIEM?

What Is SIEM?

SIEM, short for security information and event management, is a platform that gathers log and event data from across an organisation, analyses it in one place, and raises alerts when it spots signs of an attack. It combines two older ideas: security information management, which focused on storing and reporting on logs, and security event management, which focused on real-time monitoring.

A single failed login means little. Hundreds of failed logins across many accounts, followed by one success from an unusual country and a new mailbox forwarding rule, tells a clear story. Connecting those dots is what a SIEM is for, and it sits at the heart of most Security Operations Centres.

How a SIEM Works

A SIEM performs a chain of functions:

  1. Collection: logs are gathered from firewalls, servers, endpoints, identity providers, cloud platforms, email systems, and business applications, using agents, syslog, or API connectors.
  2. Normalisation: different log formats are parsed into a common schema, so that a “user” field means the same thing whichever system it came from.
  3. Enrichment: events are supplemented with context such as asset criticality, user details, geolocation, and threat intelligence.
  4. Correlation and detection: rules and analytics look for patterns across sources and time, from simple thresholds to multi-stage attack sequences.
  5. Alerting and case management: suspicious activity is raised to analysts with the supporting evidence.
  6. Search and investigation: analysts query historical data to understand what happened.
  7. Retention and reporting: logs are stored for forensic and compliance needs, and reports are produced for auditors and management.

Detection Approaches

Modern SIEMs use several techniques side by side:

Which Log Sources Matter Most

Collecting everything is expensive and creates noise. High-value sources usually include identity and authentication logs (Active Directory, Microsoft Entra ID), endpoint detection telemetry, email security events, VPN and remote access logs, firewall and proxy logs, cloud control plane logs (such as AWS CloudTrail and Azure activity logs), and logs from critical business applications. Starting with these and expanding based on detection needs gives better value than ingesting every source on day one.

Common Challenges

SIEM projects are notorious for disappointing results when poorly planned:

SIEM, SOAR, and XDR

A SIEM tells you something is wrong. SOAR platforms automate the response, running playbooks that enrich alerts, contain hosts, and open tickets. Many SIEMs now include SOAR features. Extended detection and response (XDR) platforms take a different route, correlating data mainly from one vendor’s endpoint, email, and identity products. In practice, many organisations use a SIEM as the central data platform alongside EDR or XDR tools.

Compliance Value

Centralised logging supports many requirements. PCI DSS Requirement 10 mandates logging and daily review of security events for the cardholder data environment, ISO/IEC 27001 includes logging and monitoring controls, and the NCSC’s Cyber Assessment Framework expects operators of essential services to monitor their systems for security events.

At Privia Security, we deploy and tune Security Information and Event Management (SIEM) Solutions and help you build detections that turn log data into real protection.

FAQ – Frequently Asked Questions

What Is the Difference Between SIEM and a Log Management Tool?

Log management tools collect, store, and search logs, which is valuable for troubleshooting and compliance. A SIEM goes further by normalising data, correlating events across sources in real time, applying threat intelligence and analytics, and generating security alerts with case management. Some products blur the line, but correlation and detection are what define a SIEM.

Does a Small Organisation Need a SIEM?

Not necessarily its own. Running a SIEM requires people to tune rules and respond to alerts around the clock, which is difficult for small teams. Many smaller organisations get better results from a managed detection and response service, which provides SIEM-style monitoring and expert analysts without the cost of building an in-house operation.

How Long Should SIEM Logs Be Kept?

It depends on regulatory, contractual, and investigative needs. PCI DSS requires at least 12 months of audit logs, with three months immediately available. Many incident responders recommend keeping key security logs for at least a year, because intrusions are often discovered months after they began, and older logs are essential to understanding them.

Related Terms

You May Be Interested In These

What Is Railway Signalling Security?

Cybersecurity Terms

17 November 2026

What Is Railway Signalling Security?

Read More
What Is Microsegmentation?

Cybersecurity Terms

17 November 2026

What Is Microsegmentation?

Read More
What Is System Hardening?

Cybersecurity Terms

17 November 2026

What Is System Hardening?

Read More