News · 17 September 2026

Twenty-four hours to report: the Cyber Resilience Act's reporting duties begin

On 11 September 2026 the reporting obligations of the EU Cyber Resilience Act (CRA) began to apply, three years before most of the Regulation's other requirements. Manufacturers of products with digital elements placed on the EU market must now report actively exploited vulnerabilities and severe incidents affecting the security of their products. Reports follow a staged timetable: an early warning within 24 hours of becoming aware, a fuller notification within 72 hours and a final report afterwards. They are submitted through a single reporting platform operated by ENISA and received by national CSIRTs.

Who this concerns

The Regulation covers hardware and software that connects to other devices or networks: sensors, gateways, industrial controllers, routers, smart devices and applications. It reaches manufacturers inside and outside the EU whose products are sold there. A UK company shipping an IoT gateway to customers in Italy or Germany is in scope.

What you need in place

Awareness. The clock starts when you become aware that a vulnerability is being actively exploited. That means you need a way to learn about it: monitoring of advisories, a public contact for researchers to report problems and telemetry that can reveal attacks.

Triage. Someone must decide quickly whether a report meets the threshold. Have criteria written down and a named decision-maker with a deputy.

Information. An early warning can be brief, but you must know which products and versions are affected. An up-to-date software bill of materials turns a day of detective work into a database query.

Rehearsal. Run a tabletop exercise: a researcher emails you about a flaw that is being exploited in the field. Who does what in the first hour?

Why monitoring and testing matter

You cannot report what you do not know. Independent penetration testing finds vulnerabilities before attackers do, and continuous monitoring can reveal exploitation attempts against deployed devices. Both create the evidence trail that regulators will expect to see.

Starting points for small manufacturers

  1. Publish a vulnerability disclosure policy and a monitored mailbox.
  2. Produce an SBOM for each product and keep it current.
  3. Define your internal escalation path and rehearse it.
  4. Keep a record of every decision, including reports you decided were not required.

The point is not to produce reports. It is to be the sort of manufacturer who learns about a problem in hours and has a plan.

Written in September 2026; details reflect the situation at that time.

All news