30-day money-back guarantee · Secure checkout via Stripe · Cancel monthly. Guarantee terms
Guide · Vulnerability disclosure

CRA vulnerability disclosure policy: what the Regulation asks for, and a template to adapt

Under the Cyber Resilience Act, every manufacturer of a product with digital elements needs a policy on coordinated vulnerability disclosure: a public, practical commitment setting out how external reports are received, handled and disclosed. Many pages on the topic mix up dates and article numbers. This guide lists what Regulation (EU) 2024/2847 actually says, gives a template you can copy, and shows where the policy has to be findable. It is documentation guidance, not legal advice; your team decides how the obligations apply to your products.

Updated November 14, 2026

How Attesly keeps CRA evidence per product · Attesly plans and pricing

What the Regulation asks for

Provisions of Regulation (EU) 2024/2847 that shape the policy
ProvisionWhat it requires
Annex I, Part II (5)Put in place and enforce a policy on coordinated vulnerability disclosure.
Annex I, Part II (6)Make it easy to share information about potential vulnerabilities in your product and in the third-party components it contains, including by providing a contact address for reporting them.
Article 13(17)Designate a single point of contact that users can identify easily, that lets them choose their preferred means of communication and that is not limited to automated tools.
Annex II (2)Name that single point of contact in the information that accompanies the product, and say where the policy can be found.
Annex I, Part II (4)Once a security update is available, disclose the fixed vulnerability publicly; in duly justified cases publication may wait until users have had the chance to apply the patch.
Article 13(6)Report any vulnerability you find in a component, including an open-source component, to whoever manufactures or maintains it.

Which dates apply

The essential requirements of Annex I, including the policy, apply from 11 December 2027 (Article 71(2)). The reporting obligations of Article 14 have applied since 11 September 2026, including for products placed on the market before December 2027 (Article 69(3)). In practice, you need the policy now. A researcher’s report can be the first sign of an actively exploited vulnerability, and the 24-hour clock for the early warning starts as soon as you become aware of it.

A policy template to adapt

Copy the text, replace everything in square brackets and remove what does not apply. Have the legal statement in section 7 reviewed before you publish.

  1. Our commitment. [Company] welcomes reports from security researchers, customers and partners about potential vulnerabilities in the products with digital elements we place on the market, and in the third-party components they contain.
  2. How to report. Use the form at [intake form address] or write to [security contact email]. Please include the affected product and version, steps to reproduce, your assessment of the impact and, if possible, a proof of concept.
  3. What you can expect. We acknowledge your report within [hours], provide an initial assessment and severity rating within [days], and keep you updated while we work on a fix.
  4. Fixes and disclosure. We provide security updates without delay and free of charge, and we publish information on fixed vulnerabilities: description, affected products, impact, severity and how to remediate. Where there is a justified security reason, we may delay publication until users have had the opportunity to apply the update.
  5. Scope. All products with digital elements [Company] makes available in the EU, including firmware and software, and the third-party and open-source components they contain. We report vulnerabilities in such components to whoever maintains them.
  6. Out of scope. [For example: denial-of-service tests against production systems, social engineering, physical attacks.]
  7. Legal statement. [Your statement on research carried out in line with this policy, reviewed by your counsel.]
  8. Your data. [What you store about the reporter, for what purpose and for how long.]
  9. Last updated. [Date]

Where the policy has to be findable

  • In the information and instructions that accompany each product (Annex II (2)), together with the single point of contact.
  • On your website, at a stable URL, because the user information points to it for the whole support period.
  • At the contact address itself: whoever writes to it should get to the policy without searching.

How Attesly helps

  • A pre-filled policy. The coordinated vulnerability disclosure policy is one of six document templates. Attesly fills in your company details, your public intake page, your security contact and the acknowledgement time you set, and flags every remaining gap.
  • A public intake page. Researchers report through a form on a public page; each report arrives as a draft assessment for that product.
  • Your team decides. No Article 14 case is opened automatically. When your team opens one, Attesly shows the deadlines for the early warning and the notification, counted from the awareness time you record.
  • A trust page per product, with the approved EU declaration of conformity, the end of the support period and how to report a vulnerability.

The policy template is in English. Attesly does not submit anything to ENISA or make any product compliant; your team reviews and approves every document. More on the reporting clocks: CRA Article 14 reporting.

FAQ

Does the CRA require a bug bounty?

No. Recital 76 says manufacturers should be able to use programmes that reward reports as part of their policy; Annex I requires the policy itself, not a reward.

Does the policy have to be public?

The user information has to say where the policy can be found (Annex II (2)), so in practice it is published, usually on the manufacturer's website.

Is a contact form enough as the point of contact?

Under Article 13(17), users must be able to choose their preferred means of communication, and the point of contact must not be limited to automated tools. Offering an email address alongside the form is the safer choice.

When does a report become an Article 14 notification?

When it concerns an actively exploited vulnerability in your product. The early warning is due within 24 hours of you becoming aware of it, and the notification within 72 hours.

How Attesly keeps CRA evidence per product · Attesly plans and pricing

Put your first product on file today.