Coordinating CSIRT
A Coordinating CSIRT is a national computer security incident response team that takes the lead role in facilitating multi-party vulnerability disclosures affecting multiple organisations or products. Under the CRA, EU member state CSIRTs have a defined role in coordinating vulnerability disclosures and supporting the European Vulnerability Database.
A Coordinating CSIRT is a national computer security incident response team that takes the lead role in facilitating multi-party vulnerability disclosures affecting multiple organisations or products. Under the CRA, EU member state CSIRTs have a defined role in coordinating vulnerability disclosures and supporting the European Vulnerability Database.
CVD & Vulnerability ManagementLast updated 28 October 2026
What Is a Coordinating CSIRT?
A Computer Security Incident Response Team (CSIRT) is an organised group that receives, analyses, and responds to cybersecurity incidents and vulnerability reports. A Coordinating CSIRT is one that takes an active role in facilitating the disclosure process - acting as a neutral intermediary between security researchers and affected manufacturers, particularly in multi-vendor or cross-border scenarios. The CSIRT coordinates the timeline, manages communications between parties, validates the vulnerability report, and issues a coordinated advisory. In the EU context, national CSIRTs established under the NIS2 Directive have a specific coordination mandate. ENISA maintains a directory of EU national CSIRTs and coordinates among them for EU-level issues.
CRA Role of National CSIRTs
The CRA gives the CSIRTs designated as coordinators several tasks. They receive the notifications of actively exploited vulnerabilities and severe incidents. The manufacturer sends each notification through the single reporting platform to one CSIRT and to ENISA at the same time (Article 14(1), (3) and (7)). The receiving CSIRT then sends the notification to the CSIRTs of the Member States where the manufacturer says the product has been made available (Article 16(2)). A CSIRT can ask the manufacturer for an intermediate report (Article 14(6)) and can inform users when the manufacturer fails to inform them in time (Article 14(8)). The CSIRTs also give helpdesk support on the Article 14 reporting obligations, in particular to microenterprises and SMEs (Article 17(6)).
Under the NIS2 Directive, a CSIRT designated as coordinator also acts as a trusted intermediary in coordinated vulnerability disclosure, for example when a researcher cannot reach a manufacturer. Manufacturers should find the CSIRT that Article 14(7) sets for them and establish a working relationship with it.
Major EU Coordinating CSIRTs
Several EU national CSIRTs are particularly active in coordinating vulnerability disclosures relevant to CRA-covered products:
- NCSC-NL (Netherlands): One of Europe's most active CVD coordinators, with extensive experience in multi-vendor coordinated disclosures and a publicly accessible vulnerability reporting portal.
- BSI CERT-Bund (Germany): Germany's national CSIRT, handling high volumes of vulnerability coordination relevant to industrial and IoT products.
- CERT-FR (France): ANSSI's incident response and coordination arm, with particular focus on critical infrastructure and industrial systems.
- NCSC-UK: While post-Brexit, maintains strong coordination relationships with EU CSIRTs and is relevant for manufacturers operating across both markets.
- ENISA: At the EU level, ENISA coordinates between national CSIRTs and operates the EUVDB.
When to Contact a Coordinating CSIRT
Manufacturers should consider contacting a coordinating CSIRT in the following situations:
- A vulnerability in a shared component (library, SDK, or firmware) affects multiple manufacturers' products simultaneously and coordinated disclosure is needed.
- A researcher has contacted the manufacturer through a national CSIRT and the CSIRT is facilitating the disclosure.
- The manufacturer has received a researcher report but cannot assess the impact without expert assistance.
- The manufacturer suspects a vulnerability may have national security implications.
- The manufacturer has been unable to contact a researcher who appears to be preparing to disclose a vulnerability publicly.
Pre-registering with the national CSIRT and establishing a point of contact before an incident occurs significantly reduces response latency when coordination is needed urgently.
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 there a difference between a national CSIRT and a sectoral CSIRT?+
Yes. A national CSIRT (also called a national CERT or GovCERT) covers the entire national constituency - all sectors and all organisations. A sectoral CSIRT focuses on a specific industry sector, such as financial services, healthcare, or energy. The NIS2 Directive requires member states to establish national CSIRTs; some sectors (particularly finance and energy) also have dedicated sectoral CERTs. For CRA purposes, manufacturers should engage both their national CSIRT (for general CVD coordination) and any relevant sectoral CSIRT (for sector-specific incident intelligence and coordination).
Can a manufacturer refuse to engage with a coordinating CSIRT?+
Under the CRA, manufacturers have an obligation to cooperate with competent authorities, which includes national CSIRTs in their designated role. Refusing to engage with a coordinating CSIRT facilitating a legitimate vulnerability disclosure may constitute non-cooperation with CRA requirements and could be treated as a compliance failure by market surveillance authorities. From a practical standpoint, CSIRTs that cannot engage a manufacturer will typically escalate to MSAs or proceed to support the researcher in responsible disclosure without the manufacturer's input - a much worse outcome.
Do manufacturers need to register with their national CSIRT under the CRA?+
The CRA does not mandate registration with a national CSIRT as a standalone requirement. However, manufacturers of Important Class I and II products that are also subject to NIS2 as service operators may be required to register with competent authorities under NIS2 national implementing legislation. Even without a formal requirement, proactively registering with and establishing a contact at the national CSIRT is strongly recommended as a CRA readiness best practice.
Sector checklists covering Coordinating CSIRT
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 Coordinating CSIRT fits into your complete CRA compliance programme.