CRA reporting since September 2026 — workflow and evidence checks
A working checklist for CRA Article 14 reporting, in force since 11 September 2026: platform access, CSIRT choice, roles, deadlines, user notices and older products.
By CenitiaUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
Article 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847) has applied since 11 September 2026, and ENISA's Single Reporting Platform has been operational since the same day. A manufacturer with products with digital elements on the EU market, including products placed there years ago, needs a working reporting process now. This checklist covers what to set up. For what each report must contain, see CRA reporting: early warnings, notifications and final reports.
1. Prepare platform access
The details in this step come from ENISA's Single Reporting Platform FAQ, as read on 21 November 2026.
- The platform is at portal.cra-srp.enisa.europa.eu.
- Each person who submits needs a personal EU Login account with multi-factor authentication. The account can be created in advance.
- A manufacturer has one Primary Assigned Representative and up to 20 Secondary Assigned Representatives. The Primary registers, selects the CSIRT and creates the association with the manufacturer; Secondaries join by invitation once that association is shown as verified.
- The selected CSIRT validates the association. Notifications can be submitted while validation is pending, up to 20 notifications for an unverified association.
- ENISA advises registering only when a notification has to be submitted, to limit the CSIRTs' validation workload. Decide now who the Primary will be and make sure the EU Login accounts exist.
- The platform is in English only and has no API at its initial release.
- If the platform is unavailable, submit as soon as it is back. The CSIRT can be contacted directly in the meantime, but that does not replace the submission.
2. Settle the CSIRT in advance
Article 14(7) of the Cyber Resilience Act points to the CSIRT designated as coordinator in the Member State of the manufacturer's main establishment in the Union, meaning where decisions on the cybersecurity of its products are predominantly taken or, if that cannot be determined, where it has the establishment with the most employees in the Union. A manufacturer without a main establishment in the Union follows a fixed order: the Member State of the authorised representative acting for the largest number of its products, then of the importer placing the largest number on the market, then of the distributor making the largest number available, then the Member State with the most users. ENISA warns that a notification sent to the wrong CSIRT may be invalidated and have to be resubmitted. Write the answer down before it is needed.
3. Name the people and cover the clock
The early warning is due within 24 hours of becoming aware and the notification within 72 hours. The periods are counted in hours, so the process has to work in the evening, at the weekend and during holidays. Name who decides that an event is reportable, who submits, and who stands in for each of them.
Do not rely on the platform's counters as the legal deadline. ENISA's FAQ explains that, in the current release, the 72-hour counter shows a due time 48 hours after the early warning was submitted, which can differ from 72 hours after the manufacturer became aware.
4. Define when you are "aware"
The Commission guidance on the application of the Cyber Resilience Act (C/2026/6013, paragraph 213) treats a manufacturer as aware once an initial assessment gives it a reasonable degree of certainty that a vulnerability in its product is being actively exploited or that a severe incident has compromised the security of its product. It expects the manufacturer to assess a suspicious event or a third-party report immediately. Record the time of that conclusion; every deadline is measured from it. The guidance is not legally binding.
5. Prepare the three stages and the user notice
Prepare an internal template for the early warning, the 72-hour notification and the final report. ENISA's SRP Glossary lists the fields required at each stage. Prepare the user notice at the same time: Article 14(8) of the Cyber Resilience Act requires the manufacturer to inform impacted users, and where appropriate all users, of the event and of the measures they can take.
6. Cover every product, not only new ones
Article 69(3) of the Cyber Resilience Act applies the reporting duty to all in-scope products placed on the market before 11 December 2027. The Commission guidance (paragraph 210) adds that reporting continues after a product's support period has ended. The inventory behind the process therefore has to include discontinued and out-of-support products that are still in use.
7. Test the process and keep the records
The Cyber Resilience Act does not require a rehearsal, but running one is a practical way to find out whether the people, the accounts and the templates work within 24 hours. For every real event, keep the time of awareness, the decision and its reasons, each submitted stage and the notice sent to users.
Two reporting paths and their deadlines (CRA Article 14)
Under Article 14 of the Cyber Resilience Act, a manufacturer notifies actively exploited vulnerabilities and severe incidents affecting the security of the product through the Single Reporting Platform, simultaneously to the CSIRT designated as coordinator and to ENISA. Both paths start with an early warning within 24 hours and a notification within 72 hours of becoming aware. The final stages differ: for an actively exploited vulnerability, a final report within 14 days after a corrective or mitigating measure is available (Article 14(2)(c)); for a severe incident, a final report within one month after the 72-hour notification (Article 14(4)(c)). Article 14(5) sets out when an incident is severe; there is no fixed monthly progress report. Article 14(8) also requires the manufacturer to inform impacted users. These duties have applied since 11 September 2026, including for products placed on the market before 11 December 2027 (Article 69(3)), and the platform is operational.
Existing products and modifications (CRA Article 69)
Three cases need to be kept apart under the Cyber Resilience Act. Products placed on the market before 11 December 2027 are subject to the product requirements only if they are substantially modified from that date (Article 69(2)). Article 14 reporting applies to all in-scope products, including those placed on the market earlier (Article 69(3)). Every unit placed on the market from 11 December 2027 must comply in full, even if the model is older: the Regulation applies from that date (Article 71(2)) and placing on the market is assessed for each individual unit. Units still in the stock of the manufacturer or importer that have not yet been supplied for distribution or use have not been placed on the market, so Article 69(2) does not cover them.
Primary references
FAQ
Frequently asked questions
Do I have to register on the Single Reporting Platform before an incident happens?
No. ENISA's FAQ advises manufacturers to register and start the validation of their representative only when they need to submit a notification, and says registration takes a few minutes once the person has an active EU Login account. What you can prepare in advance is the personal EU Login account with multi-factor authentication for each person who may submit, the choice of the Primary Assigned Representative and the choice of CSIRT.
What if the Single Reporting Platform is unavailable when a report is due?
ENISA's FAQ says manufacturers should wait until the platform is available again and then submit the notification. If immediate communication is necessary in the meantime, the manufacturer may contact its designated CSIRT directly, but the notification must still be submitted through the platform once it is back, as Article 14(7) of the Cyber Resilience Act requires.
Do I have to report exploitation I already knew about before 11 September 2026?
No. According to the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013, paragraph 217), the Regulation does not require retroactive reporting where the manufacturer was already aware of the active exploitation before 11 September 2026. If the manufacturer knew of the vulnerability earlier but learns of active exploitation only after that date, the reporting duty applies.
Can CRA reports be submitted automatically through an API?
Not at present. ENISA's FAQ states that no application programming interface is provided at the initial release of the Single Reporting Platform, so notifications are submitted through the platform's interface. A manufacturer can still automate its internal workflow up to that point. ENISA says an API may be considered in a later phase.
Continue reading
Related guides
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
guide
CRA Scope for Connected Devices and Their Cloud Backends
Apply the CRA remote data processing tests to connected device architectures and record external cloud dependencies separately.
5 min read
guide
When a Firmware Update Needs New CE Evidence or Retesting
Assess firmware changes against existing CE evidence, notified body notification duties and the CRA substantial modification rules with a change impact record.
6 min read
tutorial
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example
Write a scoped CycloneDX VEX decision for embedded firmware: an unresolved in_triage record, a synthetic not_affected record with justification, and reassessment triggers.
5 min read
Put this into practice
Free tools & references
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.