Definition

What is coordinated vulnerability disclosure?

Coordinated vulnerability disclosure (CVD) · also: CVD, Responsible disclosure

Short answer

A published policy and process for receiving vulnerability reports, fixing them and disclosing them in coordination with the reporter — required by CRA Annex I.

The process by which a manufacturer receives vulnerability reports from researchers, customers and other third parties, acknowledges them, remediates and discloses the fix in coordination with the reporter. Annex I Part II(5) requires manufacturers to put in place and enforce a CVD policy; Part II(6) requires a contact address. ISO/IEC 29147 describes disclosure and ISO/IEC 30111 the internal handling process; RFC 9116 (security.txt) is the conventional way to publish the contact.

Reference: Annex I Part II(5)–(6); ISO/IEC 29147; RFC 9116

Updated · Paraphrase for orientation, not legal advice.

Share:LinkedInXE-mail

Frequently asked questions

Is responsible disclosure the same as coordinated vulnerability disclosure?
They describe the same practice. 'Coordinated' is the term used by the CRA, ISO/IEC 29147 and most CERTs because it stresses that reporter and vendor agree the timing, rather than implying a judgement about either party's conduct.
Does the CRA require a bug bounty?
No. It requires a coordinated vulnerability disclosure policy and a contact address for reports. Paying bounties is optional.
What should a CVD policy contain?
Scope, how to report and in what format, what reporters can expect (acknowledgement and update times), safe-harbour terms for good-faith research, how disclosure is coordinated and credited, and the contact address — published with a security.txt file.

In practice

Related terms

Publish a vulnerability contact in minutes.

Generate an RFC 9116 security.txt, then read how to write the CVD policy Annex I Part II expects.