Cyber Resilience Act reporting duties

Since 11 September 2026, manufacturers of products covered by the EU Cyber Resilience Act (CRA) must report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform: an early warning within 24 hours, a notification within 72 hours, then a final report. The duty also covers products sold before 2027. Companies outside the EU selling software or connected devices there need the process in place now.

Cyber Resilience Act reporting duties

Topic

Compliance

Published

20 November 2026

Updated

20 November 2026

What is the Cyber Resilience Act and when does it apply?

The Cyber Resilience Act (CRA), Regulation (EU) 2024/2847, sets mandatory cybersecurity rules for software and hardware products made available in the EU, covering their planning, design, development and maintenance. The Commission’s examples include baby monitors, smartwatches, apps and computer programs. Compliant products carry the CE marking, and national market surveillance authorities enforce the rules.

The timeline is staged:

Date What applies
10 December 2024 The regulation entered into force
11 June 2026 Provisions on notifying conformity assessment bodies
11 September 2026 Article 14 reporting obligations; ENISA’s Single Reporting Platform goes live
11 December 2027 Full application: essential cybersecurity requirements, market surveillance and all other provisions

So the main product requirements are still more than a year away, but the reporting duty has applied since September 2026. This is not legal advice; we explain what the regulation says and how technical teams can prepare. Review your scope and role with legal counsel.

Does a software company outside the EU fall under it?

The CRA looks at whether a product is made available on the EU market, not where its manufacturer is established. If you sell desktop or mobile apps, embedded software, a commercial WordPress plugin or a connected device to customers in the EU, there is a good chance you are in scope. This includes companies in Türkiye, the UK, the US and elsewhere. Products not supplied in the course of a commercial activity are out of scope, and open-source software has a separate category, the open-source software steward, with lighter obligations.

SaaS is a finer line. According to the Commission’s CRA FAQs, standalone SaaS or cloud solutions designed and developed outside the responsibility of a product manufacturer are not themselves products with digital elements. But where a service meets the definition of remote data processing designed by the manufacturer for a product to work, it falls in scope. A connected device’s cloud dashboard, for example, may be assessed together with the device. The Commission says it will issue separate guidance on remote data processing.

Some products fall into the “important” (class I and II) or “critical” categories, which carry stricter conformity assessment, in some cases by a notified body. The lists are in Annexes III and IV, with technical descriptions in a separate implementing regulation.

What exactly does the reporting duty require?

Since 11 September 2026, manufacturers must report two kinds of event: actively exploited vulnerabilities in their products, and severe incidents affecting the security of their products. The deadlines on the Commission’s reporting page are:

Stage Deadline
Early warning Within 24 hours of becoming aware
Notification Within 72 hours of becoming aware
Final report (exploited vulnerability) No later than 14 days after a corrective measure is available
Final report (severe incident) Within one month of the 72-hour notification

Reports go through ENISA’s Single Reporting Platform (SRP), which ENISA brought into initial operation on 11 September 2026. Each report is addressed to the coordinating CSIRT (computer security incident response team) where the manufacturer has its main establishment, and, except in exceptional circumstances, reaches ENISA at the same time.

The Commission’s FAQs stress two points. First, under Article 69(3), the reporting duty covers products placed on the market before 11 December 2027. For those legacy products the manufacturer must report, but other obligations such as vulnerability handling do not apply unless the product is substantially modified. Second, Article 14(8) requires the manufacturer to inform affected users; if it does not do so in time, the CSIRT that received the report may inform users itself.

According to the Commission’s summary, micro and small enterprises may not be fined for missing the 24-hour early warning deadline. That relief does not extend to the 72-hour notification or the final report.

Which CSIRT does a non-EU manufacturer report to?

For companies headquartered outside the EU, this is the most practical question. ENISA’s SRP FAQ (question 18) gives the following order for manufacturers without a main establishment in the EU:

  1. The Member State where your authorised representative acts on your behalf for the highest number of products.
  2. Otherwise, the Member State where the importer places the most products on the market.
  3. Otherwise, the Member State where the distributor makes the most products available.
  4. If none apply, the Member State with the most users of the products.

The manufacturer then selects that Member State’s CSIRT designated as coordinator in the SRP. If the wrong one is chosen, the notification may be invalidated and need to be resubmitted.

Access needs preparing too. ENISA says the people who use the platform for a manufacturer need their own EU Login account with multi-factor authentication. Each manufacturer can have one primary and up to 20 secondary representatives on the platform. Twenty-four hours is not long enough to sort out accounts after an exploit notice arrives at midnight.

What process do you need to meet 72 hours?

Reporting looks like form-filling, but the hard part is that the clock starts when you become aware. These pieces need to exist before an incident:

  • Product and version inventory. A list of every product and version sold in the EU, with its third-party components. When an exploited flaw in a library is announced, you should see within minutes which of your products are affected.
  • One front door. A single address or form for vulnerability reports, automatic flagging of security keywords in support tickets, and one queue for all of it.
  • A decision owner. Who decides whether something is an “actively exploited vulnerability” or a “severe incident”, and who stands in for them.
  • Ready drafts. Pre-approved templates for the early warning, notification and user communication.
  • Timestamps. A record of when you became aware, when you decided and when you submitted.

Most of these steps can be linked with workflow automation: a flag from the support system, an inventory lookup, an alert to the owner, a pre-filled template and deadline tracking. A person should still make the call to submit. We described a similar inventory approach for AI systems in our post on the EU AI Act Digital Omnibus delay; the same inventory can serve both regulations.

Third-party components need particular attention. When an exploited flaw is announced in an open-source library you ship, and it affects your product, the reporting duty can arise for you as well. That is why a component list has to be updated with every release, not drawn up once. A flow that follows security advisories and compares them automatically with your component list makes this manageable.

What else should you prepare before December 2027?

From 11 December 2027 the whole regulation applies. According to the Commission’s FAQs, manufacturers must set a support period for each product of at least five years, unless the product is expected to be in use for less time. The end of the support period, in month and year, must be stated at the time of purchase. A cybersecurity risk assessment, a vulnerability handling process and technical documentation are also required. Importers and distributors must check the CE marking and support period information, so your EU partners will ask you for these documents.

Where should you start?

  1. List the products you sell in the EU and note whether each is in CRA scope; for SaaS, whether it meets the remote data processing definition.
  2. Build a component list per product and decide how it stays current.
  3. Work out your coordinating CSIRT using ENISA’s FAQ 18, and set up EU Login accounts and representatives now.
  4. Write down the decision owner, deputy and templates for the 24-hour, 72-hour and final reports.
  5. Run a drill: time the whole process end to end for a made-up vulnerability.

The work is most urgent for technology and software companies and manufacturers of connected products. Corrplus builds flows that link inventory, the incident queue and reporting deadlines to your existing support and development tools, and can monitor them in operation as part of managed services. See our workflow automation and digital transformation strategy pages for details, or book a free first call to talk through your situation.

Want help with this?

Book a call to apply what “Cyber Resilience Act reporting duties” describes to your company. We will listen and agree the first step together.

Frequently asked questions

We have no EU entity. Does the CRA apply to us?

It can. The CRA applies to products with digital elements made available on the EU market, wherever the manufacturer is based. For manufacturers without a main establishment in the EU, ENISA explains that the CSIRT to notify depends on where the authorised representative, importer, distributor or most users are. Confirm your position with legal counsel.

We only sell SaaS. Do we have to report?

According to the Commission's CRA FAQs, standalone SaaS or cloud solutions designed outside the responsibility of a product manufacturer are not themselves products with digital elements. If a service meets the definition of a product's remote data processing solution, it is in scope. The Commission has said separate guidance on remote data processing will follow.

Do we have to report for products sold before 2027?

Yes. Under Article 69(3), the reporting duty applies to all in-scope products, including those placed on the market before 11 December 2027. The Commission's FAQs say manufacturers must notify for such legacy products, while other duties such as vulnerability handling do not apply unless the product is substantially modified.

Where and how do we submit a report?

Reports go through ENISA's Single Reporting Platform (SRP) and reach the coordinating CSIRT and ENISA at the same time. ENISA's FAQs say the people submitting reports need their own EU Login account with multi-factor authentication. Decide who holds these accounts before an incident happens.

Related services

ServiceManaged servicesWe monitor and improve your live website, automations and AI features under a written service level agreement.
ServiceWorkflow automationWe automate the work your team moves by hand between spreadsheets, ERPs, invoicing and messaging, using n8n, Make, RPA and AI.
ServiceDigital transformation consultingWe assess processes, systems, data and people together and turn transformation into an ordered, owned and measurable plan.

Related articles

Let’s talk about your transformation

Tell us which work repeats every week. We will tell you honestly whether it is worth automating.

How we start

  1. A free first callWe pin down the problem and the goal together.
  2. A 2-week discovery sprintWe look at the data, the process and the tools, and decide where to start.
  3. A written proposalScope, architecture and timeline, in writing.

Example questions

Go straight to

CorrAI answers with AI from the content of this site and can be wrong. Please do not enter personal details. Privacy

Book a free call