Guide

What you must report under the Act, and to whom

Two things trigger a report: an actively exploited vulnerability in your product, or a severe incident affecting its security. The first notice is due within 24 hours.

Last reviewed against European Commission, National Cyber Security Centre Ireland and cyberresilienceact.eu. Sources

A desk monitor showing a plant control screen with a padlock beside it

Triggers

Two kinds of event

A manufacturer has to notify authorities when a flaw in its product is being actively exploited, or when a severe incident affects the product's security [2]. Skadden describes a severe incident as one that harms the product's ability to protect important data or functions, or leads to malicious code being introduced or run [5].

The stages

Three notices

A padlock with a tick on a hexagonal platform

Early warning

Sent inside 24 hours of the moment you are aware. The Irish regulator says it should not wait for detailed technical analysis [3].

A safe with a green shield and tick on its door

Full notification

Due within 72 hours of becoming aware, with detail such as severity, root cause and temporary mitigations [3].

A tall server rack with rows of green and red status lights

Final report

The clock differs by event. For an exploited flaw it runs to 14 days after a fix or other corrective measure exists; for a severe incident it runs to a month after the 72-hour notice [2].

A green shield with a tick above a phone showing a fingerprint

Recipients

Who is told

Reports go through ENISA's Single Reporting Platform. The notification goes to the CSIRT of the country where the manufacturer has its main establishment, and ENISA receives it at the same time unless exceptional circumstances apply [2]. Users must also be told where they are affected, with steps to reduce risk, but there is no strict deadline or format for those notices [5].

Regulatory notifications are usually not made public, though CSIRTs may alert users if a manufacturer fails to notify an exploited vulnerability in good time [5].

Limits

What is not required

The Commission guidance says vulnerabilities known before 11 September 2026 need not be reported retroactively, but reporting is needed if exploitation occurs or becomes known afterwards [7]. For a flaw in a third-party component, a report is needed only where it is actively exploited in the manufacturer's own product [7].

Reporting is not remediation

The reporting duty does not itself require you to fix the flaw, but the December 2027 duties will require risks to be handled through updates during the support period [5].

A brick wall with a flame burning through the middle

Also affected

Other regimes

CRA reporting sits beside UK and EU GDPR breach reporting, so one incident can start more than one clock [6]. Read what changed on 11 September 2026 for the practical picture.

How CyPro can help

Need a hand getting ready?

Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.

Security lead advising a board

Fractional CISO for the board

A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.

More on cypro.co.uk
Penetration tester probing an application for weaknesses

Penetration testing

A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.

More on cypro.co.uk
Cyber security consultants planning hardening work

Hardening and segmentation

Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.

More on cypro.co.uk
Security analysts monitoring systems around the clock

24/7 security monitoring

Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.

More on cypro.co.uk
Incident responders containing an attack

Incident response

If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.

More on cypro.co.uk
Scanner checking internet-facing systems for weaknesses

Vulnerability scanning

Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.

See the scanning service
Rocket launching from a cloud

Get ready

Need to know what this means for you?

Meeting the Act takes a named owner for product security, a decision path for reporting and a plan to 2027. A virtual CISO can take that role, assess which products are in scope and report progress to your board.