Which CRA product class is my product: default, important class I or II, or critical?
Last verified: 2026-11-20.
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-20.
Short answer
- The class follows the product's core functionality. If it matches a category in Annex III, the product is "important" (Class I or Class II); if it matches Annex IV, it is "critical"; otherwise it is in what the Commission calls the "default" category (CRA Art. 7(1), 8(1); Commission guidance, points 136–137, footnote 22).
- Integrating an important product as a component does not by itself make your product important (CRA Art. 7(1); Implementing Regulation (EU) 2025/2392, recitals 3–5).
- Implementing Regulation (EU) 2025/2392 gives the technical description of each category: Annex I for important products, Annex II for critical products (IR 2025/2392, Art. 2; CRA Art. 7(4)).
- Default products may use internal control (module A). Class I products may use it only if harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least "substantial" are applied in full. Class II and critical products need a third-party route (CRA Art. 32(1)–(4); Guidance, point 148).
- Free and open-source software in an Annex III category may use the default procedures if its technical documentation is public when it is placed on the market (CRA Art. 32(5)).
How the class is decided
The CRA does not define core functionality. The Commission, in guidance that is not binding, reads it as the product's main features and technical capabilities without which it could not meet its intended purpose, judged from your instructions, promotional materials and technical documentation (Guidance, points 8, 138–139). In that reading, extra functions do not change the class and a product has one core functionality for this purpose; modules you also sell separately are classified one by one; and you may not describe a product so as to misrepresent its core functionality (Guidance, points 140, 143–145). The examples in Implementing Regulation (EU) 2025/2392 are illustrative, not exhaustive (IR 2025/2392, recital 7).
The categories in the annexes
| Class | Categories (CRA annex) |
|---|
| Important, Class I | 1 identity management systems and privileged access management software and hardware, including authentication and access control readers, including biometric readers; 2 standalone and embedded browsers; 3 password managers; 4 software that searches for, removes, or quarantines malicious software; 5 products with the function of a virtual private network (VPN); 6 network management systems; 7 security information and event management (SIEM) systems; 8 boot managers; 9 public key infrastructure and digital certificate issuance software; 10 physical and virtual network interfaces; 11 operating systems; 12 routers, modems intended for the connection to the internet, and switches; 13 microprocessors with security-related functionalities; 14 microcontrollers with security-related functionalities; 15 ASICs and FPGAs with security-related functionalities; 16 smart home general purpose virtual assistants; 17 smart home products with security functionalities, including smart door locks, security cameras, baby monitoring systems and alarm systems; 18 internet-connected toys under Directive 2009/48/EC with social interactive features (e.g. speaking or filming) or location tracking; 19 personal wearables with a health monitoring purpose not covered by Regulation (EU) 2017/745 or 2017/746, or wearables intended for use by and for children (Annex III) |
| Important, Class II | 1 hypervisors and container runtime systems that support virtualised execution of operating systems and similar environments; 2 firewalls, intrusion detection and prevention systems; 3 tamper-resistant microprocessors; 4 tamper-resistant microcontrollers (Annex III) |
| Critical | 1 hardware devices with security boxes; 2 smart meter gateways within smart metering systems as defined in Article 2(23) of Directive (EU) 2019/944, and other devices for advanced security purposes, including secure cryptoprocessing; 3 smartcards or similar devices, including secure elements (Annex IV) |
The Implementing Regulation's annexes add detail: identity management includes single sign-on, one-time password and multi-factor authentication software; browsers include those with AI agent integration; password managers include browser extensions (IR 2025/2392, Annex I, Class I points 1–3). Tamper-resistant microprocessors and microcontrollers are designed to provide protection of AVA_VAN level 2 or 3 (IR 2025/2392, Annex I, Class II points 3–4). The critical categories include, where they meet the technical description, physical payment terminals, hardware security modules, Trusted Platform Modules and physical payment cards; secure elements are designed to provide protection of at least AVA_VAN.4 (IR 2025/2392, Annex II points 1, 3).
| Class | Routes allowed | Article |
|---|
| Default | Internal control (module A); EU-type examination (module B) followed by module C; full quality assurance (module H); or a European cybersecurity certification scheme, where available and applicable. You may always choose a stricter route | Art. 32(1); Guidance footnote 23 |
| Important, Class I | Any Article 32(1) route, including module A, if harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least "substantial" are applied in full. Otherwise, or if none exists: module B + C, or module H | Art. 32(2); Guidance points 148–149 |
| Important, Class II | Module B + C; module H; or a European cybersecurity certification scheme at assurance level at least "substantial" | Art. 32(3) |
| Critical | A European cybersecurity certification scheme under a delegated act adopted under Article 8(1); where the Article 8(1) conditions are not met, any Class II route | Art. 8(1), 32(4) |
| FOSS in an Annex III category | Any Article 32(1) route, if the technical documentation is made public when the product is placed on the market | Art. 32(5) |
For Class I, the Commission reads "applied in full" as applying all the requirements of a harmonised standard whose scope covers at least all the cybersecurity risks of the product's core functionality (Guidance, point 149). On 10 November 2026 the Commission extended the delivery deadline for all vertical and some horizontal standards by three months; check its standardisation page before you plan a Class I route through standards (Commission standardisation page, last update 12 Nov 2026).
These routes apply from 11 December 2027, and to products placed on the market earlier only if substantially modified from that date (CRA Art. 69(2), 71(2)). The Commission may amend Annexes III and IV by delegated act (CRA Art. 7(3), 8(2)).
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
My product includes an embedded browser. Is it an important product?
Not because of that component alone. The class follows the core functionality of your product as a whole, and integrating a product with an Annex III core functionality does not by itself change your product's procedure. You still have to assess the security of the components you integrate (CRA Art. 7(1); IR 2025/2392, recitals 3–4).
Can a Class I product use self-assessment?
Yes, if you apply in full harmonised standards whose references are published in the Official Journal, common specifications, or a European cybersecurity certification scheme at assurance level at least "substantial". Otherwise you need module B + C or module H (CRA Art. 32(2); Guidance, points 148–149).
Must critical products obtain a European cybersecurity certificate?
Only where a delegated act under Article 8(1) requires it; such an act must give at least six months' transition unless urgency justifies less. Without one, critical products follow the Class II routes (CRA Art. 8(1), 32(4)).
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. Art. 7, 8, 31, 32, 69 and 71 and Annexes III and IV read 2026-11-20.
- Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 on the technical description of the categories of important and critical products with digital elements, OJ L, 1.12.2025. Citation URL: https://eur-lex.europa.eu/eli/reg_impl/2025/2392/oj/eng. File read (OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/2d4a6388-ce5f-11f0-8da2-01aa75ed71a1.0006.01/DOC_1. Recitals 1–9, Art. 1–3, Annex I (Class I points 1–3, Class II points 3–4) and Annex II read 2026-11-20.
- 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 (OJ C PDF via the Publications Office): https://publications.europa.eu/resource/cellar/dcbc848b-e227-11f1-aefc-01aa75ed71a1.0006.01/DOC_1. Points 8 and 136–153 with footnotes 22–25 read 2026-11-20.
- European Commission, CRA standardisation page, last update 12 November 2026: https://digital-strategy.ec.europa.eu/en/policies/cra-standardisation (2026-11-20).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.