CRA-Compliant CVD Policy Template
A comprehensive CVD policy structured specifically for the EU Cyber Resilience Act. Addresses Articles 13 and 14 obligations including 24-hour early warning, 72-hour full notification, and coordinated disclosure timelines.
Last updated 25 October 2026
User Manual: How to Use This Functionality
Implementation Guide1. Purpose and Scope
This template provides the legal and technical structure for CRA-Compliant CVD Policy Template. It addresses obligations under Article 13 and Article 14 and Annex I for EU manufacturers of products with digital elements who need a CVD policy that demonstrably satisfies CRA obligations.
2. Customisation Instructions
- Replace all bracketed placeholders [LIKE THIS] with your specific details.
- Review section guidance notes to align terms with your product operations.
- Verify response timelines and single point of contact details before release.
3. Deployment and Maintenance
Publish the final document at your official documentation endpoint. Store version records for regulatory audit readiness. Review this document annually.
4. Platform Automation
CVD Portal automates this process. The platform logs vulnerability submissions, tracks response deadlines, generates CSAF advisories, and maintains an audit trail.
Unlock CRA-Compliant CVD Policy Template
Enter your work email to receive a single-use magic access link. Clicking the link in your email verifies your domain and unlocks all templates.
Key takeaways
- This template provides a comprehensive CVD policy addressing CRA Article 13 and Article 14 obligations.
- The policy covers all products with digital elements and associated cloud services placed on the EU market.
- The manufacturer commits to 48-hour report acknowledgment and a 24-hour early warning to ENISA for active exploitation.
- CSAF 2.0 advisory publication is referenced in Annex I but is not explicitly mandated for all manufacturers.
- The template accepts AI-assisted reports, explains duplicate handling, and states when a disclosure date can move earlier.
Policy Statement
Article 13(1)[COMPANY NAME] maintains a coordinated vulnerability disclosure (CVD) programme in compliance with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) and ISO/IEC 29147.
This policy governs how we receive, assess, and respond to security vulnerability reports for all [COMPANY NAME] products with digital elements. It applies to security researchers, customers, partners, and any third party who discovers a potential security vulnerability in our products.
Explicitly reference the CRA and ISO 29147. This signals to regulators, auditors, and researchers that your policy is grounded in recognised frameworks - not just a boilerplate page.
Scope
Article 13(4)This policy covers all [COMPANY NAME] products with digital elements, including:
- [PRODUCT NAME 1] (model [X], firmware [X.X] and later)
- [PRODUCT NAME 2]
- Associated cloud services and APIs at [DOMAIN]
Excluded from scope:
- Products at end-of-life (see [SUPPORT LIFECYCLE URL])
- Physical security vulnerabilities
- Third-party services not under [COMPANY NAME] control
- Vulnerabilities requiring physical access to the device
Under the CRA, your policy must cover all products with digital elements you place on the EU market. Be comprehensive - an omission here could be evidence of non-compliance.
How to Report a Vulnerability
Article 13(1)Report vulnerabilities to our security team via any of the following channels:
Preferred: Submit a report through our vulnerability disclosure portal: [PORTAL URL]
Email: [SECURITY@YOURCOMPANY.COM] PGP encryption: Key fingerprint [FINGERPRINT], available at [KEY URL]
We accept reports in English. We treat all reports as confidential.
Do not report security vulnerabilities through public forums, support tickets, or social media.
A single, clearly identified point of contact is an explicit CRA requirement (Article 13(1)). A dedicated portal creates an automatic audit trail - critical for demonstrating compliance.
What to Include in Your Report
Article 14To help us triage your report efficiently, please include:
- Affected product, model, and firmware/software version
- CWE category if known (e.g. CWE-78 OS Command Injection)
- CVSS score if you have assessed it (CVSS 3.1 or 4.0)
- Description of the vulnerability and its potential impact
- Step-by-step reproduction instructions
- Proof of concept (code, video, or screenshots)
- Whether the vulnerability is already publicly known or being exploited
- Your contact information (optional)
Asking for CVSS and CWE information helps with severity triage and populates CSAF advisories. Asking about active exploitation helps you prioritise Article 14 notification obligations.
AI-Assisted Reports
We accept reports from researchers who use AI tools, including large language models and automated analysis, to find vulnerabilities.
An AI-assisted report must include:
- The tools used, at the level of detail you are comfortable sharing
- A reproducible proof of concept that you have run yourself against the affected version
- Your own assessment of the impact, in addition to any tool output
We may close a report that contains only unverified tool output. You can re-submit it with a reproducible proof of concept.
Duplicate Reports
The same vulnerability can reach us from more than one reporter, especially when researchers use similar tools.
When we receive a duplicate report, we link it to the original report and tell the reporter that the issue is already known. We credit the first valid report in our security advisory. A later report that adds a new attack path or a wider impact is assessed as a new report.
Response Commitments
Article 13, Article 14[COMPANY NAME] commits to the following response timeline:
| Milestone | Commitment |
|---|---|
| Acknowledgment | Within 48 hours of receipt |
| Initial severity assessment | Within [5] business days |
| Status updates | At least every [30] days |
| Patch or workaround | As soon as practicable |
| Security advisory | Published upon or after patch release |
For vulnerabilities that meet the threshold for Article 14 notification (actively exploited or severe security incidents), [COMPANY NAME] will additionally notify ENISA within the timelines specified by the CRA (24-hour early warning, 72-hour full notification).
Combining your researcher commitments with a reference to Article 14 obligations in the same section demonstrates an integrated approach to vulnerability management - exactly what regulators expect.
Article 14 Notification Obligations
Article 14Where a reported vulnerability meets the threshold for mandatory reporting under Article 14 of the EU Cyber Resilience Act (i.e. the vulnerability is actively exploited, or constitutes a severe security incident), [COMPANY NAME] will:
- Submit an early warning to ENISA within 24 hours of becoming aware
- Submit a full notification to ENISA within 72 hours including severity assessment and initial remediation actions
- Submit a final report no later than 14 days after a corrective or mitigating measure is available including root cause analysis and mitigation measures
This reporting is made to the ENISA Single Reporting Platform (SRP) or the relevant national CSIRT.
Including this section in your public CVD policy serves as evidence that your organisation understands and has procedures for Article 14. It also informs researchers about what may happen when they report a critical vulnerability.
Safe Harbour
[COMPANY NAME] authorises security research conducted in good faith and in accordance with this policy. We will not pursue legal action against researchers who:
- Follow this policy
- Limit testing to what is strictly necessary to confirm the vulnerability
- Avoid intentional service disruption or data access beyond proof of concept
- Report to us before any public or third-party disclosure
We request that researchers contact us before publishing any vulnerability details.
A safe harbour statement is essential for a functioning CVD programme. Without it, researchers may avoid reporting entirely - harming the security of your products.
Coordinated Disclosure and Advisory Publication
Annex I, Article 13[COMPANY NAME] follows a coordinated disclosure model. We request [90] days from initial report to patch and publish before public disclosure.
We may publish earlier than this date when the vulnerability is independently discovered or publicly disclosed by a third party, when we have evidence that the vulnerability is actively exploited, or when a fix is available and earlier publication protects users. We will tell the reporter before we publish.
Upon resolution, we will publish a security advisory in CSAF 2.0 format (OASIS Common Security Advisory Framework) at [CSAF ADVISORY URL]. Our advisories include:
- CVE identifier (where assigned)
- CVSS severity score
- Affected products and versions
- Remediation guidance
- Acknowledgment of the reporter
Where a vulnerability affects upstream open-source or third-party components, we will coordinate disclosure with the relevant maintainers.
CSAF 2.0 advisory publication is part of the CRA's expected practices under Annex I. Mentioning it here sets expectations with researchers and signals maturity to auditors.
Supply Chain Coordination
Article 13(4)Where a reported vulnerability affects a component supplied by a third party, [COMPANY NAME] will:
- Notify the upstream component manufacturer or maintainer within [X] business days of confirming the vulnerability
- Coordinate disclosure timelines with upstream parties
- Include upstream remediation status in our security advisory
If you are reporting a vulnerability that you believe originates in an upstream component, please include component name and version in your report.
The CRA explicitly requires supply chain vulnerability coordination. Including this section demonstrates that your programme extends upstream - important for products with significant third-party component dependencies.
Publish this policy with CVD Portal
The free disclosure portal publishes your CVD policy and tracks acknowledgments. Article 14 preparation is on Reporting.
Create my free CVD portalCreate your free CVD portalFrequently asked questions
Related templates
This template is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.