CRA or NIS2: which applies to whom?
Last verified: 2026-11-21.
Information, not legal advice. Our reading of the official sources, not reviewed by a lawyer. You decide how the CRA applies to your product; for an opinion you can rely on, ask a lawyer; for a third-party conformity assessment, a notified body. This guide helps you work with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) but does not certify, assess or guarantee the compliance of any product. You remain responsible for your product's conformity assessment, CE marking and reporting. Last verified against official sources: 2026-11-21.
Short answer
- The CRA is about products. It applies to products with digital elements made available on the EU market and places obligations on the economic operators for those products: manufacturers, authorised representatives, importers and distributors. Article 2 sets no company-size threshold (CRA Art. 1, 2(1), 3(12)–(13)).
- NIS2 is about organisations. It applies to public or private entities of a type listed in its Annex I or II that are at least medium-sized and provide their services or carry out their activities in the EU, and to some entities regardless of size. It is a directive, so it reaches companies through each Member State's national law (NIS2 Art. 2(1)–(4), 41).
- One company can be under both. For example, a medium-sized or larger maker of computer, electronic or optical products (NIS2 Annex II point 5(b)) that sells a connected device, or a cloud provider (NIS2 Annex I point 8) whose service is the remote data processing solution of a product it supplies (NIS2 Annexes I–II; CRA Art. 3(1)–(2), Recital 12).
- Both laws have 24-hour and 72-hour reports, for different events. The CRA asks manufacturers to report actively exploited vulnerabilities in their products and severe incidents affecting their products' security; NIS2 asks entities to report significant incidents affecting their services. Neither text says that a report under one law counts as a report under the other (CRA Art. 14; NIS2 Art. 23).
Who is in scope
| CRA (Regulation (EU) 2024/2847) | NIS2 (Directive (EU) 2022/2555) |
|---|
| Type of act | Regulation, directly applicable in all Member States | Directive addressed to the Member States, applied through national measures |
| Applies to | Products with digital elements made available on the market, and the economic operators for them | Entities of a type listed in Annex I (sectors of high criticality) or Annex II (other critical sectors) |
| Size | No threshold in Article 2 | Medium-sized or larger; some entities regardless of size (Art. 2(2)–(4)) |
| Tiers | Important products (Annex III), critical products (Annex IV), all other products | Essential and important entities (Art. 3) |
| Main duties | Essential cybersecurity requirements (Annex I), obligations of manufacturers (Art. 13), conformity assessment and CE marking | Risk-management measures approved by the management body (Art. 20–21), incident reporting (Art. 23) |
| From when | Article 14 reporting since 11 September 2026; most other rules from 11 December 2027 | National measures to apply from 18 October 2024 |
Sources for the table: CRA Art. 2, 7, 8, 13, 71(2); NIS2 Art. 2, 3, 20, 21, 23, 41, 46.
For software companies, the closest NIS2 entries are cloud computing, data centre and content delivery network providers (Annex I point 8), managed (security) service providers (Annex I point 9), and online marketplaces, online search engines and social networking services platforms (Annex II point 6) (NIS2 Annexes I–II). The CRA notes that NIS2 applies to cloud computing services such as SaaS, PaaS and IaaS, while the CRA covers cloud functions only where they are the remote data processing solution of a product (CRA Recital 12, Art. 3(2)). The CRA's rules for remote data processing do not require measures to manage the risks to the manufacturer's network and information systems as a whole (CRA Recital 11); for entities in its scope, that organisation-wide duty is in NIS2 Article 21 (NIS2 Art. 21(1)).
Where the two laws meet
- Supply chain. NIS2 entities must cover supply chain security and "security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure", taking into account their suppliers' product quality and secure development procedures (NIS2 Art. 21(2)(d)–(e), 21(3)). The CRA says it also aims to make it easier for digital infrastructure providers to meet those supply chain requirements (CRA Recital 24).
- Certification. Member States may require NIS2 entities to use ICT products that hold a certificate under a European cybersecurity certification scheme (NIS2 Art. 24(1)). Under the CRA, a delegated act requiring certification for critical products must take account of the critical dependency of NIS2 essential entities on those products (CRA Art. 8(1)).
Incident reporting side by side
| CRA Article 14 | NIS2 Article 23 |
|---|
| Who reports | The manufacturer of the product | The essential or important entity |
| What | An actively exploited vulnerability in the product; a severe incident having an impact on the security of the product | A significant incident: severe operational disruption or financial loss for the entity, or considerable damage to others |
| To whom | The CSIRT designated as coordinator and ENISA, through ENISA's single reporting platform | The entity's CSIRT or, where applicable, its competent authority |
| Early warning | Within 24 hours of becoming aware | Within 24 hours of becoming aware |
| Notification | Within 72 hours of becoming aware | Within 72 hours of becoming aware |
| Final report | Vulnerability: no later than 14 days after a corrective or mitigating measure is available. Severe incident: within one month after the incident notification | Within one month after the incident notification; a progress report instead if the incident is still ongoing |
| Telling others | Inform impacted users and, where appropriate, all users | Notify the recipients of the services where appropriate |
Sources for the table: CRA Art. 14(1)–(5), (7)–(8); NIS2 Art. 23(1), (3)–(4).
Neither Article 14 of the CRA nor Article 23 of NIS2 says that a report under one law satisfies the other. Our conservative reading: if you are a manufacturer and also a NIS2 entity, and one event meets both triggers, plan for both reports. The CRA encourages Member States to consider national single entry points for reporting under the CRA, NIS2, the GDPR and other EU law (CRA Recital 72). The Commission's CRA guidance, which is not binding, aligns its reading of "becoming aware" with the NIS2 implementing rules (Guidance, points 8, 212).
NIS2 may change. In January 2026 the Commission proposed targeted amendments (COM(2026) 13), and on 21 November 2026 the European Parliament's procedure file still showed the proposal at committee stage (Commission proposal page; procedure 2026/0012(COD)).
To check this for your product with an AI assistant, add Shieldbook to Claude or connect the Shieldbook MCP server (https://shieldbook.ppftec.com/mcp); the scope check is also at https://shieldbook.ppftec.com/check.
FAQ
Does NIS2 apply to my company just because I make software?
Not by that alone. NIS2 applies to entities of a type listed in its Annexes I and II that meet its size rule or one of its exceptions, through your Member State's national law (NIS2 Art. 2, 41, Annexes I–II). The CRA applies to your software product if you make it available on the EU market (CRA Art. 2(1)).
Does my NIS2 incident report also count as my CRA report?
Neither text says so. CRA reports go through ENISA's single reporting platform to the coordinating CSIRT and ENISA; NIS2 reports go to your CSIRT or competent authority (CRA Art. 14(1), (3), (7); NIS2 Art. 23(1)). Check whether your Member State offers a single entry point (CRA Recital 72).
My customers are NIS2 entities. Do I have NIS2 duties?
NIS2 duties fall on the entities in its scope. They must take into account their suppliers' product quality and cybersecurity practices (NIS2 Art. 21(3)), so they may ask you for evidence. Your duties as a product manufacturer come from the CRA (CRA Art. 13).
Sources
Opened by the compliance analyst; dates are when each source was last read.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024. Citation URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/21b7d4eb-a6e2-11ef-85f0-01aa75ed71a1.0006.01/DOC_1. Recitals 11–13, 24, 66 and 72 and Art. 1–3, 7, 8, 13, 14, 16 and 71 read 2026-11-21.
- Directive (EU) 2022/2555 (NIS2), OJ L 333, 27.12.2022, p. 80. Citation URL: https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/9b84d482-85bd-11ed-9887-01aa75ed71a1.0006.01/DOC_1. Art. 1–3, 20–24, 41 and 46 and Annexes I–II read 2026-11-21.
- European Commission, Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act), Communication C/2026/6013, OJ C, 17.11.2026, not binding (point 8). Citation URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:C_202606013. File read: https://publications.europa.eu/resource/cellar/dcbc848b-e227-11f1-aefc-01aa75ed71a1.0006.01/DOC_1. Points 8 and 209–224 read 2026-11-21.
- European Commission, Proposal for a Directive as regards simplification measures and alignment with the Cybersecurity Act, COM(2026) 13, library page published 20 January 2026: https://digital-strategy.ec.europa.eu/en/library/proposal-directive-regards-simplification-measures-and-alignment-cybersecurity-act (2026-11-21).
- European Parliament, Legislative Observatory, procedure file 2026/0012(COD): https://oeil.europarl.europa.eu/oeil/en/procedure-file?reference=2026/0012(COD) (2026-11-21).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.