Key facts
- Basis in the CRA
- Annex I, Part II, points 5 and 6
- Also in the user information
- A single point of contact for reporting vulnerabilities (Annex II)
- Usual location
- A page such as /security, linked from security.txt
- Bug bounty
- Not required
What the Cyber Resilience Act asks for
Two points of Annex I, Part II deal with disclosure. Point 5 requires you to put in place and enforce a coordinated vulnerability disclosure policy. Point 6 requires you to make it easy to share information about potential vulnerabilities, including by providing a contact address for reports. Annex II adds that the user information must include a single point of contact where vulnerabilities can be reported and where your policy can be found.
Coordinated means you and the reporter agree on timing: you get a chance to fix the problem before details go public, and the reporter gets credit and a predictable process.
What a good policy includes
- Scope: which products, versions and domains are covered, and what is out of scope.
- How to report: one address or form, and what to include, such as affected version, steps to reproduce and impact.
- What you commit to: when you acknowledge a report, when you give a first assessment, how you keep the reporter informed.
- Coordination and publication: how long you usually need to fix, when details are published, and how reporters are credited.
- Good-faith research: a statement that you won’t pursue people who follow the policy, within the limits of the law.
- What not to do: no access to other users’ data, no denial-of-service testing, no social engineering of staff.
Template
Copy it, replace the brackets, and publish it at a stable URL.
# Security and vulnerability disclosure
We welcome reports of security vulnerabilities in [product names].
## Scope
In scope: [apps, versions, domains, backend APIs].
Out of scope: [third-party services, social engineering, denial of service].
## How to report
Email [security@example.com] or use [form URL].
Please include the affected product and version, steps to reproduce,
and the impact you observed. Encrypt sensitive details with [key URL] if needed.
## What to expect
- We acknowledge your report within [3 working days].
- We send a first assessment within [10 working days].
- We keep you informed until the issue is fixed.
## Disclosure
We aim to fix confirmed vulnerabilities within [90 days] and publish an
advisory once an update is available. We credit reporters who wish to be named.
## Good-faith research
If you follow this policy, we won't take legal action against you for your
research. Don't access other users' data, disrupt the service,
or test against people.
Last updated: [date]
How it fits with security.txt
The policy explains the process; security.txt tells tools and people where to find it. Put your reporting address in the Contact field and the policy URL in the Policy field, and keep both in sync when either changes.
Voluntary reports and mandatory reporting
Your disclosure policy covers reports you receive, about any vulnerability. Article 14 covers reports you send to authorities, for vulnerabilities that are actively exploited and for severe incidents. A single case can trigger both. When a researcher tells you a flaw is already being used in attacks, start the Article 14 clock while you work through your normal process.
After you publish it
Test the reporting address once a quarter, make sure more than one person can read it, and record each report and its outcome. That log becomes evidence for the vulnerability-handling part of your Annex I checklist.
Questions
Does the CRA require a vulnerability disclosure policy?
Yes, for products in scope. Annex I, Part II requires manufacturers to put in place and enforce a coordinated vulnerability disclosure policy and to make it easy to report vulnerabilities, including by providing a contact address.
Do I need a bug bounty programme?
No. A disclosure policy says how to report and how you will respond. Paying rewards is a separate choice the CRA doesn’t require.
How fast do I have to reply to a report?
The CRA doesn’t set a reply time for incoming reports. Choose response times you can keep, publish them in the policy, and meet them. Article 14 deadlines apply separately if the vulnerability turns out to be actively exploited.
Where should the policy live?
On a stable page of your website, linked from the Policy field of your security.txt file and from your app’s support or legal pages.
Sources
- Regulation (EU) 2024/2847, Annex I Part II and Annex II, EUR-Lex
- RFC 9116: A File Format to Aid in Security Vulnerability Disclosure
This guide explains the regulation in general terms. It isn’t legal advice for your product.