← CRA Glossary
CVD & Vulnerability Management

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.

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.

CVD & Vulnerability Management

Last updated 17 October 2026

What Is a Vulnerability Disclosure Policy?

A Vulnerability Disclosure Policy (VDP) is a formal, published document that establishes the rules of engagement between a manufacturer and the security researcher community. It tells researchers: where to submit vulnerability reports; what information to include; what the manufacturer commits to doing in response (acknowledgement timeline, triage timeline, fix timeline); what constitutes in-scope and out-of-scope research; and what legal protections researchers can expect. A VDP is the operational specification for an organisation's coordinated vulnerability disclosure process. Without a published VDP, researchers have no reliable basis for trusting that their report will be handled appropriately, and many will simply publish their findings rather than report them privately.

CRA reference:

CRA Requirements for a VDP

The CRA's requires manufacturers to put in place and enforce a policy on coordinated vulnerability disclosure. Recital 63 provides additional context, noting that manufacturers must make it possible for security researchers, users, and others to report vulnerabilities through accessible channels. A CRA-compliant VDP must at minimum: designate a contact channel (email address or web form) for receiving vulnerability reports; state acknowledgement and response timelines; define the manufacturer's approach to coordinating with the reporter before public disclosure; include a safe harbour clause protecting good-faith researchers from legal action; and be publicly accessible. The policy should also be referenced from the product's security.txt file for discoverability by automated security research tools.

CRA reference:, Recital 63

VDP vs Bug Bounty vs CVD Policy

These three terms are sometimes used interchangeably but have distinct meanings. A VDP (Vulnerability Disclosure Policy) is the policy document - it defines the rules. A CVD policy is sometimes used synonymously with VDP, or may refer more specifically to the process for handling reports once received. A bug bounty programme is an optional financial incentive layer on top of a VDP - it rewards researchers with cash or recognition for valid findings. The CRA mandates a VDP (or equivalent CVD policy); a bug bounty is optional and complementary. Running a bug bounty without the underlying policy infrastructure is insufficient for CRA compliance, and maintaining a VDP alone - without a financial reward - fully satisfies the CRA obligation.

CRA reference:

Operationalising Your VDP

Publishing a VDP is the first step; operating it is the continuous obligation. An effective VDP operation requires:

  • Monitored inbox: The disclosed contact channel must be actively monitored - ideally with an SLA of within one business day for initial triage.
  • Acknowledgement within 5 days: ENISA's CVD Good Practice Guide and industry standards expect acknowledgement within five business days of report receipt.
  • Triage process: Reported vulnerabilities must be assessed for validity, severity (using CVSS or EPSS), and remediation priority.
  • Researcher communication: Keep reporters updated on progress - silence breeds public disclosure.
  • Resolution tracking: Log all reports, their disposition, and timeline to demonstrate compliance to MSAs.

CVD Portal automates the intake, triage routing, and resolution tracking components of VDP operation.

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 standard template for a VDP?+

Several widely used templates exist. ENISA published a CVD Good Practice Guide with example policy language. disclose.io maintains a community-driven repository of VDP templates at disclose.io. The ISO/IEC 29147 standard on vulnerability disclosure provides normative guidance on what a VDP should contain. Section 2.7.5 of the OWASP DevSecOps Guideline also outlines maturity stages and operational triage SLAs for VDPs and bug bounty programmes. CVD Portal provides a customisable VDP template that meets CRA requirements as part of its onboarding workflow.

How long should the disclosure timeline be in a VDP?+

Most industry practice and ENISA guidance aligns on 90 days as the standard disclosure timeline - the period during which the manufacturer should fix the vulnerability before the researcher is entitled to publish. The CRA does not mandate a specific number of days. Some organisations use 45 or 60 days for critical vulnerabilities, or extend beyond 90 days for complex systemic issues. The VDP should state the timeline clearly and explain the conditions under which it may be extended.

Must a VDP be available in all EU official languages?+

The CRA does not explicitly require VDPs to be translated into all EU official languages. However, Annex II user information must be provided in the language(s) required by the member states where the product is sold. For practicality, most manufacturers publish their VDP in English (the common language of the security research community) and consider providing key elements in the primary language(s) of their main markets.

Sector checklists covering Vulnerability Disclosure Policy (VDP)

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.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)).IoT Sensors & Connected DevicesIoT sensors - temperature, humidity, pressure, flow, and motion sensors - are the backbone of industrial and building automation. Most fall into the Default CRA class, but their constrained hardware often makes meeting Annex I security requirements challenging. Manufacturers must plan for secure update mechanisms even on resource-constrained devices.

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 Vulnerability Disclosure Policy (VDP) fits into your complete CRA compliance programme.

View checklists →