CRA reporting portal: prepare the upstream workflow
From 11 September 2026, manufacturers of products with digital elements must use ENISA’s Single Reporting Platform for mandatory notifications of actively exploited vulnerabilities and severe incidents under Article 14 of the Cyber Resilience Act. ENISA describes the SRP as a report-once mechanism: the manufacturer selects the relevant coordinating CSIRT, and the notification can then be made available to ENISA and disseminated to other relevant authorities.
That removes routing friction. It does not remove the operational problem that precedes submission. Before a manufacturer can make a defensible notification, it still has to establish which product and versions are affected, whether exploitation meets the CRA trigger, what is known about impact and mitigation, and who owns the regulatory decision.
Review prompts drawn from this analysis and its role brief. These identify evidence to examine, not completed verification.
| Review lens | Decision or boundary | Evidence and constraints |
|---|---|---|
| Engineering architecture | Bind regulated products to released versions, components, supplier owners and deployed populations. | Exercise incomplete-evidence scenarios so assumptions and uncertainty can be recorded without stopping the workflow. |
| Cybersecurity boundary | Keep the CRA reporting trigger distinct from generic vulnerability presence and preserve the basis for affected/not-affected conclusions. | Retain a reviewable timeline of evidence, assumptions and decision authority for later updates and audit. |
| Operational decision | Assign product scope, exploitability inputs and escalation authority before the reporting clock starts. | Measure readiness as evidence latency from signal to owned product decision, not as portal completion time. |
CRA reporting clocks: measure evidence latency
The engineering metric that matters is therefore not portal completion time. It is evidence latency: how long it takes to move from an external or internal vulnerability signal to a product-scoped, reviewable decision.
A usable operating model links product identity, deployed software versions, component inventory, supplier ownership, exploitability assessment, mitigations and decision authority. SBOM and VEX can support that chain, but neither replaces product-specific analysis or accountable judgement.
The practical test is whether the organisation can produce a bounded statement while some evidence is still incomplete, preserve the uncertainty explicitly, and update the record as stronger evidence arrives.
- Map every regulated product to versions, components and responsible owners.
- Define the trigger and owner for the first exploitability assessment.
- Predefine escalation authority for the 24-hour decision window.
- Record uncertainty, assumptions and supplier dependencies explicitly.
- Exercise the workflow end to end before a real notification.
Sources & further reading
Continue this decision.
Move from this analysis into a curated route across related incidents, evidence and operating constraints.
