← CRA Glossary
Incident Response & Operations

Security Operations Centre (SOC)

A Security Operations Centre (SOC) is a centralised function staffed by security analysts who monitor, detect, analyse, and respond to cybersecurity incidents and threats in real time. For manufacturers of CRA-covered products, internal SOC capabilities or managed SOC services support the continuous monitoring and incident response obligations required by the CRA.

A Security Operations Centre (SOC) is a centralised function staffed by security analysts who monitor, detect, analyse, and respond to cybersecurity incidents and threats in real time. For manufacturers of CRA-covered products, internal SOC capabilities or managed SOC services support the continuous monitoring and incident response obligations required by the CRA.

Incident Response & Operations

Last updated 19 July 2026

What Is a Security Operations Centre?

A Security Operations Centre (SOC) is a dedicated organisational function responsible for the continuous monitoring of an organisation's security posture, detection of threats and incidents, and coordination of incident response. SOCs are staffed by security analysts working in shifts (often 24/7 for large organisations), supported by technology tools including SIEM platforms, EDR solutions, threat intelligence feeds, and automation playbooks. SOC analysts investigate alerts, correlate events across multiple data sources, determine whether a genuine security incident has occurred, and escalate to incident response teams. For manufacturers of CRA-covered products, the SOC function is relevant both for protecting the manufacturer's own infrastructure (including development and signing infrastructure) and for supporting the monitoring obligations relevant to CRA Article 14 notifications.

CRA reference:Article 14

SOC Functions Relevant to CRA Obligations

Several SOC capabilities directly support CRA compliance:

  • Exploitation monitoring: SOC analysts monitoring threat intelligence feeds and telemetry can detect evidence that a vulnerability in the manufacturer's products is being actively exploited - triggering the CRA Article 14 24-hour notification obligation.
  • Product security telemetry: For cloud-connected products, the SOC may monitor product telemetry for signs of compromise or anomalous behaviour that could indicate an exploited vulnerability.
  • Manufacturing and signing infrastructure protection: The SOC monitors the manufacturer's internal infrastructure, including the build pipeline and signing servers. A compromised signing key - not detected by the SOC - could result in malicious firmware being signed and distributed to customers.
  • Incident escalation to PSIRT: When the SOC identifies a security event related to a product vulnerability, it should have a defined escalation path to the PSIRT team responsible for CRA Article 14 notifications and remediation.
CRA reference:Article 14

SOC vs PSIRT: Different but Complementary

The SOC and PSIRT are distinct functions that must collaborate for effective CRA compliance:

  • SOC: Monitors the organisation's infrastructure and detects threats in real time. Focuses on the organisation as the target. Responds to active incidents.
  • PSIRT: Manages the vulnerability lifecycle for the manufacturer's products. Receives researcher reports, triages CVEs, coordinates remediation, and publishes advisories. Focuses on the product as the subject.

The interfaces between them are: the SOC escalates to PSIRT when it detects evidence of product vulnerability exploitation; the PSIRT escalates to the SOC when it needs infrastructure security support during incident response. Both contribute to the CRA Article 14 notification process - the SOC provides exploitation evidence; the PSIRT provides the vulnerability context and notification drafting.

CRA reference:Article 14

When Is a SOC Required for CRA Manufacturers?

The CRA does not mandate a SOC specifically. However, the obligation to notify ENISA within 24 hours of becoming aware of actively exploited vulnerabilities effectively requires some form of continuous monitoring capability. For smaller manufacturers, this might be a lightweight monitoring capability with automated alerting for critical threat intelligence events rather than a full 24/7 SOC. Manufacturers subject to NIS2 as operators have more explicit monitoring obligations that may require SOC-level capabilities.

  • Managed SOC / MSSP: Outsource SOC functions to a Managed Security Service Provider. Provides 24/7 monitoring without internal staffing.
  • Threat intelligence subscription with alerting: Subscribe to threat intelligence feeds that send alerts for new exploitation events affecting the manufacturer's product technology stack.
  • CSIRT partnership: Establish a notification arrangement with the national CSIRT to receive proactive alerts when exploitation of the manufacturer's products is detected.

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

Does a manufacturer need a 24/7 SOC for CRA compliance?+

Not necessarily. The CRA's 24-hour notification obligation for actively exploited vulnerabilities requires that the manufacturer can receive and act on exploitation intelligence at any time - but this can be achieved through automated alerting systems, on-call arrangements, and threat intelligence subscriptions rather than a fully staffed 24/7 SOC. The appropriate level of monitoring investment depends on the product's risk profile: manufacturers of Important Class products in critical sectors should have more robust monitoring than default-class consumer product manufacturers.

Can a manufacturer use a managed SOC provider for CRA compliance monitoring?+

Yes. Managed Security Service Providers (MSSPs) offering SOC-as-a-service can provide the monitoring capabilities needed for CRA compliance. The manufacturer must ensure the MSSP's service covers the specific monitoring needs - product telemetry, exploitation intelligence for the manufacturer's specific technology stack, and clear escalation paths to the PSIRT and executive team. The manufacturer retains legal responsibility for CRA notifications - the MSSP's role is detection and alerting, not regulatory compliance.

What is the difference between a SOC and a CERT/CSIRT?+

A SOC focuses on real-time monitoring and detection within an organisation. A CERT/CSIRT (Computer Emergency Response Team / Computer Security Incident Response Team) focuses on coordinated incident response, often including external coordination with other affected parties, government authorities, and the security research community. Many large organisations have both: the SOC provides the continuous monitoring layer; the CSIRT provides the structured incident response capability that is activated when a significant incident occurs. For CRA purposes, both functions are relevant but the PSIRT is the primary product-security response function.

Sector checklists covering Security Operations Centre (SOC)

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 Operations Centre (SOC) fits into your complete CRA compliance programme.

View checklists →