Published

EU Cyber Resilience Act (CRA) reporting is already in effect for covered manufacturers. Since September 11, 2026, they must report actively exploited vulnerabilities and severe incidents affecting the security of products with digital elements. Build a controlled case that connects awareness, affected products, assessment, each submitted report, and the corrective work that follows.
The European Commission's reporting guidance explains the staged deadlines and submission through ENISA's Single Reporting Platform (SRP). The first report is an early warning. Later notifications and final reports add information as the response progresses, so retain what was known and submitted at each stage.
The Commission's CRA summary describes the scope around hardware and software products made available on the EU market, with specific exclusions. The reporting rules also cover in-scope products placed on the market before the broader December 11, 2027 application date. Record the manufacturer's identity, product and version population, components, and relevant markets.
Apply the CRA's event criteria: active exploitation requires reliable evidence of malicious exploitation, while a severe incident is assessed against the product-security severity criteria. Keep internal ticket severity and CRA classification as separate fields with a recorded rationale. ENISA's SRP FAQ explains these notification types and points to the detailed guidance.
The Commission identifies a later December 11, 2027 reporting start for the distinct open-source software steward role. Determine the organisation's role and the product's scope explicitly. For the wider purchasing and product-assurance questions, see the CRA guide for document-platform buyers.
The Commission's reporting guidance summarises the following limits. The early warning and 72-hour notification are required without undue delay, within their stated maximum windows. Use the relevant trigger for each stage and record how its deadline was calculated.
| Stage | Timing and trigger |
|---|---|
| Early warning | Within 24 hours of becoming aware of the actively exploited vulnerability or severe incident. |
| Vulnerability or incident notification | Within 72 hours of awareness of the relevant reportable event. |
| Final report: actively exploited vulnerability | No later than 14 days after a corrective or mitigating measure becomes available. |
| Final report: severe incident | Within one month after the 72-hour incident notification. |
Keep the first signal, supporting evidence, awareness assessment, and internal review times in the case history. An internal approval step must not be used to postpone the awareness-based clock. If later facts change the assessment, preserve the earlier record and document the correction. Complete root-cause analysis can continue while the team prepares the information required for the current reporting stage.
Identify the event, affected product population, evidence, responsible officers, and reporting clocks.
Prepare the stage-specific package, submit through the SRP, and connect the submitted version to its confirmation.
Link new findings, measures, further submissions, communications, and closure evidence to the case.
ENISA's current FAQ states that the SRP initial release has no submission API. Automate internal collection and preparation where useful, then have an Assigned Representative submit through the interface. Representatives use personal EU Login accounts with MFA; arrange a usable handover and backup role. ENISA also notes that portal drafts are specific to the individual representative's account.
Keep an approved handover package available internally. Use the current ENISA reporting resources and glossary for the fields required at each stage. Separate known facts, estimates, and information still being investigated, with an owner for the next update.
The following is a practical case-file design. It supports preparation and later review alongside the fields required by the current SRP forms.
A working draft can change frequently. Give each issued report its own retained record so later analysis does not silently replace what was submitted. Restrict exploit evidence and personal information according to their audience; the status view used by operational teams may need a narrower summary.
This fictional exercise assumes the manufacturer becomes aware of a reportable actively exploited vulnerability at 16:10 UTC on Friday. Product firmware versions 4.2–4.4 are initially assessed as affected. All example times use UTC; the 24-hour maximum falls at 16:10 Saturday and the 72-hour maximum at 16:10 Monday. The example times illustrate the maximum windows; the workflow also needs to address reporting without undue delay.
Case INC-2026-00041 links the exploitation evidence, product catalogue, release records, and security ticket. The reporting officer records the assumed awareness event and calculated deadlines. Internal review assignments retain their own timestamps without resetting the reporting clock.
The team prepares and reviews the available stage-specific information. At 20:00 Friday, an Assigned Representative submits through the SRP interface. The case retains the issued content, submission time, and platform confirmation or reference. Investigation continues against a new working version.
By 18:00 Sunday, the investigation has updated the affected population and mitigation information. The representative submits the notification and links it to the same event. The case preserves both submitted versions and explains the changed facts; any correction to an earlier submission is recorded through the applicable SRP update process.
A corrective measure becomes available on Tuesday. The owner records that event, the relevant release and validation evidence, and the final-report deadline based on the 14-day rule. The communication owner links approved user guidance and its issue history to the case.
The reporting owner prepares the final package and the representative submits it within the applicable deadline. The file connects the issued report, confirmation, corrective measure, and later follow-up. Closing the reporting task and closing any continuing investigation are recorded as separate decisions.
A severe-incident case follows its own assessment and final-report trigger. Keep the notification type and stage visible throughout the workflow. The cyber risk register guide covers the separate question of how investigation and treatment evidence inform ongoing risk decisions.
A useful CRA reporting workflow connects the event, awareness record, product population, stage-specific submission, and corrective measures. Prepare information internally, use the current SRP submission route, and preserve the issued record as later findings develop.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.