SECURITY.md or security.txt for the CRA: which one
As of 6 October 2026, the Cyber Resilience Act (Regulation (EU) 2024/2847) requires manufacturers to put in place a coordinated vulnerability disclosure policy and to provide a contact address for vulnerability reports (Annex I, Part II, points 5 and 6), and to tell users the single point of contact (Annex II). It names neither file: SECURITY.md and security.txt are common ways to publish them. The Regulation's main duties apply from 11 December 2027.
What each file is
| SECURITY.md | security.txt | |
|---|---|---|
| Where | Repository root, .github/ or docs/; GitHub shows it in the Security tab | https://your-domain/.well-known/security.txt |
| Format | Free Markdown | Standard fields (RFC 9116): Contact, Expires required |
| Who finds it | People on GitHub | Researchers and tools that check a domain |
| Named in the CRA | No | No |
What the Regulation asks
- A policy on coordinated vulnerability disclosure, enforced (Annex I, Part II, point 5).
- Measures that facilitate sharing information about vulnerabilities, including a contact address for reporting (Annex I, Part II, point 6).
- Public disclosure of fixed vulnerabilities once a security update is available (Annex I, Part II, point 4).
- User information that includes the single point of contact for reports and where the disclosure policy can be found (Annex II).
The single point of contact must be easily identifiable and must not be limited to automated tools (Article 13(17)), so offer a mailbox or form that people read, not only a machine-readable file. A bare contact address is not a policy; the policy should say what reporters can expect and how disclosure is coordinated.
What to do
- Write a short disclosure policy: scope, how to report, what the reporter can expect, disclosure timing. Use the policy template.
- Put it in
SECURITY.mdfor the repository, with the contact and a link to private reporting if you enable it on GitHub. - Publish
security.txton the product's website with aContact:and anExpires:date, and aPolicy:link to the same policy. Generate it with the security.txt tool. - Use one contact in both places, and make sure someone reads it.
- Add the contact and policy link to the user information (Annex II).
- Run the repository check to see whether your repository shows a policy.
If you are the manufacturer, reports about actively exploited vulnerabilities also go to the CSIRT and ENISA under Article 14; see reporting obligations.
Article references
Annex I, Part II, points 4 to 6; Annex II; Article 14.
This is general information, not legal advice. Having these files does not make a product compliant or certified.
Free tools
- Product classifier: Is your product in scope, and in which category?
- SBOM checker: Check a CycloneDX or SPDX file in your browser.
- security.txt and disclosure policy: The contact file and policy the Regulation expects.
- Repository check: what a GitHub repository already shows.
Information generated from your inputs, with article references to Regulation (EU) 2024/2847. It is not legal advice and does not replace your own assessment; check the references against the Official Journal.