Skip to main content
Europe’s New Data Breach Reporting Rules: The Cyber Resilience Act | Pillsbury - Global Sourcing Practice - JD Supra

Europe’s New Data Breach Reporting Rules: The Cyber Resilience Act | Pillsbury - Global Sourcing Practice - JD Supra

Data Breaches
16 lis 2026, 17:03Google News Cybersec
Oryginał
3 min read

Europe's Cyber Resilience Act (CRA) has introduced new incident reporting requirements that took effect on September 11, 2026, adding to the growing number of cybersecurity obligations for businesses operating in the EU.

Businesses operating in the EU face a growing number of cybersecurity reporting requirements that can apply to the same event. The latest addition is the Cyber Resilience Act (CRA), which covers a broad range of hardware and software made available in the EU and requires manufacturers to report actively exploited vulnerabilities and severe incidents affecting product security. These reporting duties do not depend on personal data being involved.

A single cyber incident can set several reporting clocks running simultaneously. An attack on a software product might expose personal data, disrupt a regulated service and involve an actively exploited vulnerability. Businesses must assess each applicable regime and meet its deadlines, often while still investigating what happened.

CRA Reporting Triggers

The CRA establishes two distinct reporting triggers. An actively exploited vulnerability requires reliable evidence that a malicious actor has exploited a vulnerability in the product without the system owner's permission. Discovering a vulnerability through testing or responsible disclosure does not, by itself, trigger mandatory reporting.

A severe incident does not require evidence of an actively exploited vulnerability. The test includes incidents that compromise, or could compromise, the product's ability to protect sensitive or important data or functions. It also includes incidents that have led, or could lead, to malicious code being introduced or executed in the product or a user's systems.

Multiple Reporting Obligations

Suppose a software manufacturer discovers that an attacker has exploited a vulnerability in its product. The attack also exposes personal data for which the manufacturer is the controller and disrupts an essential service it operates. The manufacturer may need to assess three separate obligations: a CRA report for the exploited vulnerability, a GDPR notification for the personal data breach and, if it is an in-scope entity, a NIS2 notification for the service disruption.

Determining when each reporting clock starts can be as difficult as deciding whether the event is reportable. The regimes use different awareness, detection and classification tests, as well as different thresholds and reporting procedures. A business may need to submit an initial report before it understands the full incident, then provide updates as evidence emerges.

Future Reporting Simplification

The European Commission's Digital Omnibus proposal would establish an ENISA-maintained single entry point for certain reports under NIS2, the GDPR and DORA, as well as other EU digital regulations. It would also raise the GDPR threshold for notifying a supervisory authority to breaches likely to result in a 'high risk' to data subjects' rights and freedoms and extend the GDPR reporting deadline from 72 to 96 hours.

The proposal would also allow a manufacturer's CRA severe-incident report to satisfy specified NIS2 reporting requirements where the CRA report contains the required information under NIS2. This would address duplicate reporting where both obligations apply; it would not remove other applicable NIS2 duties.

Preparation Steps

Organizations should map applicable requirements by identifying the regimes that apply to each entity, product, service and jurisdiction, including the CRA reporting duties now in force. They should create a common escalation process that brings security, product, privacy and legal teams into the assessment promptly.

Businesses must track each deadline by recording when the relevant awareness, detection or classification threshold was met, and organize the initial response around the earliest applicable deadline. They should also prepare coordinated notifications and document reporting decisions to ensure consistency as investigations develop.

Z.ai
Article written by AI
Z.ai GLM-4.5-FlashFree
Free AI articles150 of 150
No limit after signing in with Telegram