← CRA Glossary
CVD & Vulnerability Management

CVD Coordinator

A CVD Coordinator is a neutral third party - typically a CSIRT, CERT, or specialised organisation - that facilitates the coordinated disclosure process between security researchers and manufacturers, particularly in multi-vendor or complex vulnerability scenarios. Under the CRA, ENISA plays a CVD coordination role for the EU.

A CVD Coordinator is a neutral third party - typically a CSIRT, CERT, or specialised organisation - that facilitates the coordinated disclosure process between security researchers and manufacturers, particularly in multi-vendor or complex vulnerability scenarios. Under the CRA, ENISA plays a CVD coordination role for the EU.

CVD & Vulnerability Management

What Is a CVD Coordinator?

A CVD Coordinator acts as a neutral intermediary in the vulnerability disclosure process, facilitating communication between the reporting researcher and one or more affected manufacturers. Coordinators are typically called upon when: the researcher cannot identify or reach the affected manufacturer; multiple manufacturers are affected by the same vulnerability and coordinated simultaneous disclosure is needed; the researcher and manufacturer cannot agree on timelines or scope; or the vulnerability is particularly complex or sensitive (e.g., affecting critical infrastructure). Major CVD coordinators include CERT/CC (Carnegie Mellon), NCSC-NL, BSI (Germany), CISA (US), and national CSIRTs across the EU. ENISA has a coordination function specifically for the CRA's European vulnerability database.

CRA reference:Article 35, Article 14

The CVD Coordinator's Role in the Process

When engaged, a CVD coordinator typically:

  • Validates the report: Confirms the vulnerability is genuine and reproducible before engaging vendors, reducing noise and protecting researcher credibility.
  • Identifies affected parties: Determines which manufacturers, vendors, or components are affected - particularly important for supply chain vulnerabilities.
  • Manages communication: Acts as a single point of contact for the researcher, relaying information to multiple vendors and managing separate bilateral communications.
  • Sets and manages the timeline: Establishes a coordinated disclosure date that gives all affected parties adequate time to develop fixes simultaneously.
  • Mediates disputes: Resolves disagreements about scope, severity, or timeline between researchers and vendors.
  • Issues coordinated advisories: Publishes a master advisory that references all affected products' individual advisories, enabling comprehensive user awareness.
CRA reference:Article 35

ENISA's Coordination Role Under the CRA

The CRA assigns ENISA a specific CVD coordination function at the EU level. ENISA operates the European Vulnerability Database (EUVDB), which aggregates vulnerability information from national CSIRTs, manufacturers, and other sources. ENISA can facilitate coordination between researchers and manufacturers when national-level coordination is insufficient - particularly for vulnerabilities with cross-border impact. ENISA also issues guidance on CVD best practices and supports national CSIRTs in developing their coordination capabilities. For manufacturers operating across multiple EU member states, understanding ENISA's coordination mechanisms is important: a vulnerability reported through any EU national CSIRT may be escalated to ENISA-level coordination if its impact warrants it.

CRA reference:Article 35, Article 14

When to Involve a CVD Coordinator

Manufacturers should consider proactively engaging a CVD coordinator in the following situations:

  • A reported vulnerability affects components or libraries also used by other manufacturers.
  • The researcher is unresponsive or unreachable after initial contact.
  • The vulnerability affects safety-critical or critical infrastructure systems where simultaneous multi-vendor disclosure is essential.
  • The researcher and manufacturer are in dispute about the disclosure timeline or scope.
  • The vulnerability has national security implications that require government coordination.

Manufacturers should pre-establish relationships with relevant national CSIRTs before incidents occur. Knowing the coordination process in advance significantly reduces response time when a complex multi-party disclosure scenario arises.

CVD Portal makes CVD Coordinator compliance straightforward.

Public CVD submission portal, acknowledgment tracking, Article 14 deadline alerts, and CSAF advisory generation. Receiving and tracking reports is free for all manufacturers placing products with digital elements on the EU market. Article 14 filing with the SRP-ready package is on Pro.

Start your free portal

Frequently asked

How does a security researcher contact a CVD coordinator?+

Most national CSIRTs publish contact details on their official websites and accept vulnerability reports through encrypted channels. CERT/CC accepts reports at [email protected]. ENISA's EUVDB portal provides a submission interface. The disclose.io and FIRST.org directories list contact information for coordinators worldwide. Researchers should contact coordinators when they cannot reach the affected manufacturer directly or when they believe the vulnerability requires multi-party coordination due to its scope.

Is involving a CVD coordinator required under the CRA?+

No. The CRA does not require manufacturers to use a CVD coordinator for ordinary vulnerability disclosures. Coordinators are optional facilitators used when direct coordination between researcher and manufacturer is insufficient or impractical. However, when a vulnerability affects multiple products or has systemic impact, ENISA or national CSIRTs may initiate coordination even without a manufacturer's request, particularly if the manufacturer has not responded to the researcher's report within expected timeframes.

Does using a CVD coordinator mean giving up control of the disclosure?+

Not entirely, but coordinators do introduce a third party into the process. Reputable coordinators (national CSIRTs, CERT/CC) are committed to facilitating coordinated disclosure and will not publish details unilaterally before an agreed date unless there is evidence of active exploitation or bad faith by a vendor. Manufacturers should treat coordinator engagement as a collaborative process, provide timely responses to coordinator queries, and negotiate timeline and disclosure scope as they would directly with a researcher.

Related terms

Coordinated Vulnerability Disclosure (CVD)CVD is the process by which a security researcher privately reports a vulnerability to the affected vendor, who then develops and releases a fix before the vulnerability is made public. Under the EU Cyber Resilience Act, manufacturers of products with digital elements are legally required to establish a CVD process.Coordinating CSIRTA 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.CSIRT - Computer Security Incident Response TeamA CSIRT is a team that coordinates responses to cybersecurity incidents, typically operating at a national or sector level. Under the CRA, manufacturers must notify the relevant national CSIRT within 24 hours of discovering an actively exploited vulnerability in their product, alongside simultaneous notification to ENISA.ENISA - EU Agency for CybersecurityENISA (the European Union Agency for Cybersecurity) is the EU's dedicated cybersecurity agency, headquartered in Athens with offices in Brussels. Under the CRA, ENISA operates the central EU vulnerability registry, receives Article 14 notifications of actively exploited vulnerabilities, and publishes guidance supporting manufacturer compliance.Vulnerability Disclosure Policy (VDP)A Vulnerability Disclosure Policy (VDP) is a published document that defines how an organisation receives, handles, and responds to vulnerability reports from external security researchers. Under the CRA, maintaining a VDP is a legal requirement for all manufacturers of products with digital elements.Disclosure TimelineA disclosure timeline is the agreed or stated period between a security researcher privately reporting a vulnerability to a manufacturer and the point at which either the fix is released or the vulnerability is publicly disclosed. The standard industry timeline is 90 days, though the CRA does not prescribe a specific period.

Browse the full CRA Compliance Checklist

See how CVD Coordinator fits into your complete CRA compliance programme.

View checklists →