CRA vs NIS2 — when both apply and how to handle the overlap
The CRA regulates products; NIS2 regulates entities. Who falls under each, how their 24-hour and 72-hour reporting duties differ, and where GDPR breach notification fits.
By CenitiaUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
The Cyber Resilience Act (Regulation (EU) 2024/2847) regulates products with digital elements and the manufacturers, importers and distributors that supply them. The NIS2 Directive (Directive (EU) 2022/2555) regulates organisations: entities in listed sectors must secure the network and information systems they use and report significant incidents. A hardware manufacturer can fall under both, under the Cyber Resilience Act for what it sells and under NIS2 for how it runs its own operations. One event can then require a report under the Cyber Resilience Act, a report under NIS2 and a notification under the GDPR. Each has its own trigger, recipient and deadline, and filing one does not discharge the others.
Who NIS2 covers (Directive (EU) 2022/2555, Articles 2 and 3)
NIS2 applies to public or private entities of a type listed in its Annex I or Annex II that are medium-sized enterprises or larger within the meaning of Commission Recommendation 2003/361/EC and that operate in the Union (Article 2(1)). Some entities are covered whatever their size (Article 2(2)).
Annex II point 5, "Manufacturing", lists:
- manufacture of medical devices and in vitro diagnostic medical devices;
- manufacture of computer, electronic and optical products (NACE Rev. 2 division 26);
- manufacture of electrical equipment (division 27);
- manufacture of machinery and equipment not elsewhere classified (division 28);
- manufacture of motor vehicles, trailers and semi-trailers (division 29);
- manufacture of other transport equipment (division 30).
An Annex II entity that does not qualify as essential under Article 3(1) is an "important entity" (Article 3(2)). A medium-sized or larger electronics manufacturer established in the EU is therefore typically an important entity under NIS2, as well as a manufacturer under the Cyber Resilience Act.
NIS2 is a directive. Member States had to adopt national measures by 17 October 2024 and apply them from 18 October 2024 (Article 41). The obligations, the competent authority and the reporting channel come from the national law that applies to the entity, so read that law and not only the Directive. The Cyber Resilience Act is a regulation and applies directly.
What NIS2 requires of the entity (Directive (EU) 2022/2555, Article 21)
Article 21 requires essential and important entities to take appropriate and proportionate technical, operational and organisational measures to manage the risks to the network and information systems they use. The minimum list in Article 21(2) includes incident handling, business continuity, supply chain security, security in the acquisition, development and maintenance of systems (including vulnerability handling and disclosure), cryptography, access control and multi-factor authentication.
Supply chain security is where the two acts meet in practice. Under Article 21(3), an entity that assesses its suppliers takes into account the vulnerabilities specific to each direct supplier and the overall quality of its products and cybersecurity practices. Customers that are NIS2 entities therefore have a reason to ask a manufacturer about the security of its products, which is the subject of the Cyber Resilience Act.
Reporting duties compared
| Cyber Resilience Act, Article 14 | NIS2, Article 23 | GDPR, Article 33 | |
|---|---|---|---|
| Who reports | Manufacturer of a product with digital elements | Essential or important entity | Controller |
| Trigger | Actively exploited vulnerability in the product, or severe incident having an impact on the security of the product | Significant incident: severe operational disruption of services or financial loss for the entity, or considerable damage to other persons (Article 23(3)) | Personal data breach, unless unlikely to result in a risk to the rights and freedoms of natural persons |
| Recipient | CSIRT designated as coordinator and ENISA, through the Single Reporting Platform | National CSIRT or, where applicable, competent authority | Competent supervisory authority |
| First stage | Early warning within 24 hours of becoming aware | Early warning within 24 hours of becoming aware | Notification without undue delay and, where feasible, within 72 hours of becoming aware |
| Second stage | Notification within 72 hours of becoming aware | Incident notification within 72 hours of becoming aware | None |
| Final stage | Vulnerability: within 14 days after a corrective or mitigating measure is available. Incident: within one month after the 72-hour notification | Final report within one month after the incident notification; if the incident is still ongoing, a progress report then and a final report within one month of handling it | None |
| Others to inform | Impacted users (Article 14(8)) | Recipients of the services, where appropriate (Article 23(1) and (2)) | Data subjects, where the breach is likely to result in a high risk (Article 34) |
The NIS2 column describes the Directive. National transposing laws set the actual procedure and may add detail.
Handling one event under several regimes
- Record when you became aware. Each deadline runs from awareness under its own rules.
- Ask three separate questions. Is a vulnerability in our product being actively exploited, or is there a severe incident affecting the security of our product (Cyber Resilience Act)? Has an incident significantly affected our own services or operations (NIS2)? Has personal data been breached (GDPR)?
- Report to each recipient that applies. A notification on the Single Reporting Platform does not reach the NIS2 authority or the data protection authority.
- Keep the decisions, the reasons and the submissions in one incident record.
Two illustrations. A firmware flaw in a router that attackers are exploiting in customers' networks is a matter for Article 14 of the Cyber Resilience Act even if the manufacturer's own systems are untouched. Ransomware that stops the manufacturer's production can be a significant incident under NIS2 without involving any vulnerability in a product.
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.
Personal data breach notification (GDPR, Articles 33 and 34)
Under Article 33(1) of the General Data Protection Regulation (Regulation (EU) 2016/679), a controller notifies a personal data breach to the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. A notification made after 72 hours must give the reasons for the delay. Where the breach is likely to result in a high risk, Article 34 also requires the controller to tell the data subjects without undue delay.
Not every security incident is a personal data breach, and not every personal data breach has to be notified. Keep a record of the assessment in both cases.
Primary references
FAQ
Frequently asked questions
Can a company be subject to both the CRA and NIS2?
Yes. The Cyber Resilience Act (Regulation (EU) 2024/2847) applies to a company as the manufacturer, importer or distributor of products with digital elements. NIS2 (Directive (EU) 2022/2555) applies to it as an organisation if it is of a type listed in Annex I or II of the Directive and is a medium-sized enterprise or larger. The two sets of duties are separate: one concerns the product, the other the company's own network and information systems.
Are electronics manufacturers covered by NIS2?
Annex II point 5 of Directive (EU) 2022/2555 lists the manufacture of computer, electronic and optical products (NACE Rev. 2 division 26), electrical equipment (division 27) and machinery (division 28), among others. Under Article 2(1) the Directive applies to such entities if they are medium-sized enterprises or larger, and Article 3(2) classes them as important entities unless they qualify as essential. The detailed rules are in the national law that transposes the Directive.
Does a CRA report through the Single Reporting Platform also satisfy NIS2?
No. A report under Article 14 of the Cyber Resilience Act goes through ENISA's Single Reporting Platform to the CSIRT designated as coordinator and to ENISA, and concerns an actively exploited vulnerability or a severe incident affecting a product. A NIS2 report under Article 23 of Directive (EU) 2022/2555 goes to the national CSIRT or competent authority under national law and concerns a significant incident affecting the entity's own services. If one event meets both tests, both reports are due.
Is NIS2 directly applicable like the CRA?
No. NIS2 is a directive: Member States had to adopt national measures by 17 October 2024 and apply them from 18 October 2024 (Article 41 of Directive (EU) 2022/2555), so an entity's obligations come from national law. The Cyber Resilience Act is a regulation and applies directly in every Member State: Article 14 reporting since 11 September 2026 and the product requirements from 11 December 2027.
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.