ENISA's CRA Single Reporting Platform: how to be ready to report
By SBOMBox SBOM experts · · 3 min readShort answer: since 11 September 2026, manufacturers report actively exploited vulnerabilities and severe incidents under the Cyber Resilience Act through ENISA's Single Reporting Platform (SRP). Register before you need it, and have the product data ready, because the first deadline is 24 hours.
What the Single Reporting Platform is
The SRP is the one EU entry point for CRA notifications. You submit once; the report is routed to the CSIRT acting as coordinator in your Member State, and ENISA receives it at the same time. ENISA describes the September launch as an initial operating capability, and it has been updated since: ENISA's page records an upgrade to version 1.2.1 on 20 October 2026. Check the ENISA SRP page for the current documentation before you train your team on screenshots.
What it accepts today
- Mandatory notifications from manufacturers under Article 14: actively exploited vulnerabilities and severe incidents affecting the security of a product with digital elements.
- Notifications under Article 24 from open-source software stewards, where that applies.
- Voluntary reports (for example, vulnerabilities that are not yet exploited, or near misses). Sources disagree on whether this is live yet, so confirm in ENISA's FAQ.
The clocks you are working against
- 24 hours from becoming aware: an early warning.
- 72 hours: a vulnerability or incident notification with more detail and any mitigations.
- 14 days after a corrective measure is available (vulnerabilities), or one month after the notification (severe incidents): a final report.
The full sequence is in our step-by-step guide to the 24-hour rule.
What to prepare before the first report
- An account and named submitters. Do not let the only login belong to one person who is on holiday.
- Your main establishment in the EU, which decides the coordinating CSIRT. Non-EU manufacturers should know which rule applies to them.
- A product register: product names, versions on the market, and the support period for each.
- An SBOM per released version, stored where you can search across products. This is how you answer 'which versions contain the exploited component?' inside 24 hours.
- A short template for the early warning: product, affected versions, what you know, whether exploitation is suspected to be malicious, and any immediate mitigation.
- A rota. Twenty-four hours includes weekends and public holidays.
Rehearse it
Pick a recent high-profile CVE and run a tabletop exercise: who notices, who confirms exposure, who drafts, who submits. Time each step. Most teams find the slow part is not the form, it is working out which releases are affected. If that takes more than an hour, fix the inventory first.
You can see how complete your current SBOMs are with the free SBOM checker, which scores their quality across 8 categories.
This is general information, not legal advice. Confirm how the rules apply to your products with counsel.