← CRA Glossary
Incident Response & Operations

Security Information and Event Management (SIEM)

SIEM (Security Information and Event Management) is a platform that aggregates, correlates, and analyses security log data from across an organisation's infrastructure to detect threats, support incident investigation, and provide audit evidence. SIEM is a core technology in SOC operations and supports CRA-related monitoring and incident detection.

SIEM (Security Information and Event Management) is a platform that aggregates, correlates, and analyses security log data from across an organisation's infrastructure to detect threats, support incident investigation, and provide audit evidence. SIEM is a core technology in SOC operations and supports CRA-related monitoring and incident detection.

Incident Response & Operations

Last updated 19 July 2026

What Is SIEM?

Security Information and Event Management (SIEM) is a technology platform that collects security-relevant log data from across an IT environment - servers, network devices, endpoints, applications, and cloud services - and correlates that data to detect threats and anomalies. SIEM platforms provide real-time alerting when log patterns match known attack signatures or anomalous behaviour baselines; centralised log storage for forensic investigation; compliance reporting by demonstrating audit trails; and dashboards for security operations teams to monitor the security posture. Major SIEM platforms include Splunk, Microsoft Sentinel, IBM QRadar, and open-source options such as Wazuh and OpenSearch (formerly OpenDistro for Elasticsearch). Cloud-native SIEM services have largely replaced on-premises deployments for new implementations.

CRA reference:Article 14

SIEM for CRA Manufacturer Compliance

For manufacturers operating under CRA obligations, SIEM serves several compliance-relevant functions:

  • Build and signing infrastructure monitoring: The development pipeline and firmware signing infrastructure are high-value targets for supply chain attacks. SIEM monitoring of these systems can detect anomalous access patterns, configuration changes, or unusual signing activity that might indicate compromise.
  • Exploitation detection: SIEM correlation rules can detect patterns in product telemetry or network monitoring data that suggest a published vulnerability in the manufacturer's products is being exploited against their infrastructure or customers.
  • Incident investigation support: When a security incident occurs that may trigger CRA Article 14 notifications, SIEM provides the log data needed for rapid investigation and accurate incident characterisation.
  • Audit trail for compliance: SIEM provides tamper-resistant log storage that creates an auditable record of security events - evidence that may be requested by MSAs during compliance investigations.
CRA reference:Article 14

Key Log Sources for CRA Manufacturers

The SIEM's value depends on the quality and completeness of its log sources. Priority log sources for CRA manufacturers include:

  • Source code management: Git event logs - commits, branches, pull requests, and access control changes - to detect unauthorised code modifications.
  • CI/CD pipeline: Build logs, dependency resolution events, signing operations, and deployment actions.
  • Signing infrastructure: HSM usage logs, code signing operations, and key access events.
  • Vulnerability management tools: Dependency-Track and PSIRT system events - new high/critical findings, status changes, notification submissions.
  • Product telemetry (where applicable): For cloud-connected products, aggregated telemetry indicating exploitation patterns or anomalous usage.
  • Corporate network: Standard firewall, endpoint, and identity provider logs for detecting infrastructure compromises that could affect the development environment.

SIEM vs SOAR: Understanding the Distinction

SOAR (Security Orchestration, Automation, and Response) extends SIEM by automating response actions triggered by SIEM alerts. Where SIEM detects and alerts, SOAR automatically executes response playbooks - for example, automatically isolating a compromised device, creating a PSIRT ticket for a new critical vulnerability finding, or drafting a ENISA notification based on a confirmed exploitation alert. For CRA manufacturers with high alert volumes or strict notification timelines, SOAR automation reduces the time between detection and response:

  • A SOAR playbook can automatically create a PSIRT triage ticket when Dependency-Track raises a new Critical finding.
  • A SOAR playbook can automatically prepare an Article 14 notification draft and route it for senior review when an exploitation alert fires, reducing the manual effort required to meet the 24-hour deadline.
  • Response automation must be designed carefully to avoid false-positive triggers that result in erroneous regulatory notifications.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is a SIEM required for CRA compliance?+

The CRA does not mandate a SIEM specifically. However, the obligation to detect and notify ENISA of actively exploited vulnerabilities within 24 hours effectively requires monitoring capabilities that would typically be delivered by a SIEM or equivalent. For small manufacturers, lightweight monitoring solutions and automated threat intelligence alerting may suffice. For manufacturers with Important Class products or significant cloud infrastructure, a SIEM is the standard mechanism for achieving the monitoring depth required.

Can product telemetry from deployed devices be fed into a SIEM?+

Yes, and this is valuable for exploitation detection at scale. If a manufacturer's products send telemetry to a cloud backend, security-relevant events (authentication failures, unexpected network requests, anomalous API usage) can be aggregated and fed into the SIEM for correlation. This requires: defining which product events are security-relevant during product design; ensuring the telemetry pipeline sends events to the SIEM in a parseable format; and developing SIEM detection rules for exploitation patterns relevant to the product's known vulnerability classes.

How long should SIEM log retention be for CRA compliance purposes?+

The CRA requires manufacturers to retain technical documentation for ten years after the last product unit is placed on the market. While SIEM logs are not explicitly included in the technical file, they form part of the security monitoring evidence that demonstrates ongoing CRA compliance. Security-relevant SIEM logs should be retained for at least the duration of the product's support period plus the time needed for any regulatory investigation. In practice, 12-24 months of hot storage plus archival to cold storage for the full retention period is a common and cost-effective approach.

Sector checklists covering Security Information and Event Management (SIEM)

Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Hospital IT & Clinical Information SystemsHospital IT systems are not excluded from the CRA by the MDR carve-out. The category includes electronic health record (EHR) systems, clinical information systems, and hospital information systems (HIS). It also includes clinical decision support tools not classified as Software as a Medical Device (SaMD). These systems are critical to patient care, process sensitive patient data at scale, and face sophisticated threat actors. Most are default-class products, because classification follows core functionality (Article 7(1)) and Annex III lists no healthcare software category. Patient data scale and the role in patient care raise the risk that the Article 13(2) risk assessment must address.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Security Information and Event Management (SIEM) fits into your complete CRA compliance programme.

View checklists →