The Cyber Resilience Act, Regulation (EU) 2024/2847, sorts products with digital elements into four tiers. Everything in scope is "default" unless it has the core functionality of one of the 19 class I or 4 class II categories of Annex III, which make it "important", or of the 3 categories of Annex IV, which make it "critical". The tier decides the conformity assessment route, not whether the Regulation applies. The Annexes name each category in a line. Article 7(4) told the Commission to specify the technical description of each, and Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 does so in two annexes: published in the Official Journal on 1 December 2025, in force since 21 December 2025.
The descriptions are the text a notified body and a market surveillance authority classify against. The Commission's guidance on the application of the Regulation, C(2026) 5252 of 27 July 2026, section 6, says how to read them. This article gives both: the six rules of the guidance with its examples, and all 26 descriptions verbatim, in the Official Journal's own wording for this language.
The test: core functionality
Paragraph 139 of the guidance: "The core functionality of a product with digital elements refers to that product's main features and technical capabilities, without which it would not be able to meet its intended purpose." It is assessed "in light of that product's specific context and conditions of use", taking into account "the information the manufacturer supplies in the instructions for use, promotional or sales materials and statements, as well as in the technical documentation". Recital 2 of the Implementing Regulation says the same in one sentence: under Articles 7(1) and 8(1), "the core functionality of a product with digital elements determines whether that product with digital elements meets the technical description of a category".
Six rules follow, each with an example in the guidance.
1. Ancillary functions do not change the tier. Paragraph 140: products "often, if not always, perform additional functions that do not contribute to the product's core functionality", and performing functions "other than or additional to" a category's description "does not in itself prevent the product from having one such core functionality". Recital 4 of the Implementing Regulation gives the example: operating systems "often include software that performs ancillary functions not included in the technical description of that product category, such as calculators or simple graphics editors".
2. Integrating an important or critical product does not make you one. Paragraph 141, citing Article 7(1): "the mere integration of an important or critical product with digital elements does not in itself render the product with digital elements an important or critical product". Example 58 is a smartphone: it integrates an operating system, but "the smartphone as a whole has a different core functionality". Recital 3 of the Implementing Regulation uses a news app with an embedded browser, which is not thereby a browser, while the manufacturer must still "evaluate the security of the whole product, considering, as appropriate, the security of the components".
3. Substantially more, or substantially less, is a different product. Paragraph 142: a product may resemble a category "yet their core functionality may substantially exceed or fall substantially short" of it. Example 59: SOAR software can do what a SIEM does, but its core functionality "substantially exceeds that of a SIEM, including services such as incident response", so it "is generally not considered to have the core functionality of SIEM systems". Example 60: log collection and visualisation tools that show dashboards "do not perform data correlation, nor do they provide actionable security insights", so they fall short of a SIEM. Additional functions that "merely complement or enhance" a core functionality that does match do not take the product out.
4. You may not describe your way out. Paragraph 143: a manufacturer "may not misrepresent the core functionality" to escape a stricter regime, "e.g. by overly emphasising or downplaying the role of certain functionalities", and "clear inconsistencies between promotional materials, instructions for use, and technical documentation" are how that would show.
5. One core functionality per product, written into the technical file. Paragraph 144: a product "may not have more than one core functionality for the purposes of determining the applicable conformity assessment regime", and since Annex VII requires the intended purpose and the conformity procedure to be described, "the product's core functionality should therefore be clearly identified".
6. Modules sold separately are products of their own. Paragraph 145: where modules of a suite "are offered for separate purchase, licensing or subscription", each "constitute[s] standalone products with digital elements in their own right" classified by its own core functionality. Example 61 is a security suite whose SIEM module is class I, whose intrusion detection module is class II, and whose analytics module is default. Modules "supplied solely as components of an integrated product with digital elements and not made available separately" are classified at the level of the integrated product.
What the tier changes, and what it does not
Section 6.2 restates Article 32. Default products always have the internal control route, module A. Class I products have it only where a harmonised standard, common specification or certification scheme at assurance level substantial is applied in full; paragraph 149 adds that "the standard's scope needs to cover at least all the cybersecurity risks associated to that product's core functionality", and paragraph 151 that risks of additional functions must then be covered "via other means" and documented. Example 62 is an antivirus with disk-cleaning and anti-tracking functions: a harmonised standard for the core, additional measures for the rest, and the internal control route for the whole. Example 63 is a router with an integrated firewall: classified as a router, class I, even though firewalls are class II, because "it is the core functionality of the product with digital elements as a whole, and not the functionality of the integrated components taken in isolation, that determines" the tier (paragraph 152). Class II and critical products need a notified body or a certification scheme, with the open-source exception of Article 32(5). Paragraph 146 notes that getting Article 32 wrong "may trigger administrative fines in accordance with Article 64(3)".
None of this touches the reporting duty: Article 14 applies to every tier alike.
The 26 descriptions, verbatim
The category names are Annex III and IV of the Regulation; the descriptions are Annex I and II of the Implementing Regulation, footnote markers removed, paragraphs joined. Where the Official Journal says "this category includes but is not limited to", it is listing examples, not defining the category.
| Ref | Category (Annex III / IV) | Technical description (Implementing Regulation 2025/2392) |
|---|---|---|
| III.I.1 | Identity management systems and privileged access management software and hardware, including authentication and access control readers, including biometric readers | Identity management systems are products with digital elements that provide mechanisms for authentication or authorisation and that may also provide mechanisms for the lifecycle management of identity credentials of natural persons, legal persons, devices or systems, such as identity registration, provisioning, maintenance, deregistration. These systems include access management systems that control access of natural persons, legal persons, devices or systems to digital resources or physical locations. Privileged access management software is an access management system that controls and monitors access rights to IT or OT systems and sensitive information within an organisation, including systems enforcing differentiated access control policies for privileged users. This category includes but is not limited to authentication and access control readers, biometric readers, single sign-on software, federated identity management software, one-time password software, hardware authentication devices such as transaction authentication number (TAN) generators, authentication software and multi-factor authentication software. |
| III.I.2 | Standalone and embedded browsers | Software products with digital elements that enable end users to access, render, and interact with web content and services hosted on servers that are connected to networks such as the Internet. They typically include a browser engine for interpreting and displaying content written in markup language (e.g. HTML), support for web protocols (e.g. HTTP, HTTPS), the ability to execute scripts and manage user inputs as well as storage of temporary or persistent data from websites (cookies). This category includes but is not limited to standalone applications that fulfil the functions of browsers, embedded browsers intended for integration into another system or application as well as browsers with AI agent integration. |
| III.I.3 | Password managers | Products with digital elements that store passwords, locally on a device or on a remote server, including activities such as generation of passwords as well as password sharing and integration with local or third-party applications for usage of passwords. This category includes but is not limited to local password managers, password managers provided as browser extensions, enterprise password managers as well as hardware-based password managers. |
| III.I.4 | Software that searches for, removes, or quarantines malicious software | Software products with digital elements, typically referred to as antivirus or antimalware, that detect or search for malicious software or code on devices, or remove or quarantine such software or code, in order to maintain the integrity, confidentiality, or availability of such devices. In the context of this category of products, malicious software means software containing malicious features or capabilities that can cause harm directly or indirectly to the user and/or the computer system, such as viruses, worms, ransomware, spyware and trojans. This category includes but is not limited to software that detects or searches for malicious software in real-time or manually, rootkit detection and rescue disks with the core functionality of searching, removing or quarantining malicious software. |
| III.I.5 | Products with digital elements with the function of virtual private network (VPN) | Products with digital elements that establish an encrypted logical tunnel that is constructed from the system resources of a physical or virtual network. This category includes but is not limited to virtual private network clients, virtual private network servers and virtual private network gateways. |
| III.I.6 | Network management systems | Products with digital elements that manage connected network elements, such as servers, routers, switches, workstations, printers or mobile devices, by monitoring them and controlling their network operations and configuration. This category includes but is not limited to end-to-end management systems and dedicated configuration management systems, such as controllers for software-defined networking. |
| III.I.7 | Security information and event management (SIEM) systems | Products with digital elements that collect data from multiple sources, analyse and correlate that data and present it as actionable information for security-related purposes, such as threat and incident detection, forensic analysis or compliance purposes. |
| III.I.8 | Boot managers | Software products with digital elements that manage the process of initial system startup after power on/restart by initialising hardware, loading or transferring control to the operating system environment or system resources, and selecting boot options. This category includes but is not limited to UEFI firmware, single-stage and multi-stage boot loaders. |
| III.I.9 | Public key infrastructure and digital certificate issuance software | Products with digital elements used as part of a public key infrastructure (PKI) that manage the validation, creation, issuance, distribution, status publication, renewal or revocation of digital certificates, or the generation, storage, escrow, exchange, destruction or rotation of cryptographic keys associated with such digital certificates. This category includes but is not limited to key management systems, digital certificate management systems, online certificate status protocol responders and all-in-one PKI solutions. |
| III.I.10 | Physical and virtual network interfaces | Physical network interfaces are products with digital elements that directly connect a device to a network via an application programming interface (API) provided by the interface drivers, typically operating at the data link layer, and that feature hardware adapters to transmission media with corresponding firmware, typically operating at the physical and data link layer. Virtual network interfaces are products with digital elements that directly or indirectly connect a device to a network via an API that emulates that of drivers of physical network interfaces, typically operating at the data link layer. This category includes but is not limited to wired and wireless network interface cards, controllers and adapters, such as for Wi-Fi, Ethernet, IrDA, USB, Bluetooth, NearLink, Zigbee, or Fieldbus, as well as purely virtual standalone products, such as virtual network interface cards, container network interfaces and VPN interfaces. |
| III.I.11 | Operating systems | Software products with digital elements that provide an abstract interface of the underlying hardware and control the execution of software, and that may provide services such as computing resource management and configuration, scheduling, input-output control, managing data, and providing an interface through which applications interact with system resources and peripherals. This category includes but is not limited to real-time operating systems, general-purpose and special-purpose operating systems. |
| III.I.12 | Routers, modems intended for the connection to the internet, and switches | Routers are products with digital elements that establish and control the flow of data between different networks by selecting paths or routes using routing protocol mechanisms and algorithms, typically operating at the network layer. This category includes but is not limited to wired and wireless routers, virtual routers and routers with or without modems. Modems intended for the connection to the Internet are hardware products with digital elements that use digital modulation and demodulation techniques to convert analogue signals from and to digital signals for IP-based communication. This category includes but is not limited to fibre modems, Digital Subscriber Line (DSL) modems, cable (DOCSIS) modems, satellite modems and cellular modems. Switches are products with digital elements that provide connectivity between networked devices through packet forwarding mechanisms and that have a management plane, typically implemented at the data link or network layer. This category includes but is not limited to managed switches, smart switches, multilayer switches, virtual security switches, programmable switches for software-defined networking and bridges such as wireless access points. |
| III.I.13 | Microprocessors with security-related functionalities | Products with digital elements that are integrated circuits that carry out central processing functions relying on external memory and peripherals, including microcode and other low-level firmware. They additionally provide security-related functionalities, such as encryption, authentication, secure key storage, random number generation, trusted execution environment, or other hardware-based protection mechanisms, that aim to secure other products, networks or services beyond the microprocessor itself, such as secure boot chain, virtualization or secure communication interfaces. |
| III.I.14 | Microcontrollers with security-related functionalities | Products with digital elements that are integrated circuits that carry out central processing functions integrating memory allowing the microcontroller to be programmable and typically also other peripherals, including microcode and other low-level firmware. They additionally provide security-related functionalities, such as encryption, authentication, secure key storage, random number generation, trusted execution environment, or other hardware-based protection mechanisms, that aim to secure other products, networks or services beyond the microcontroller itself, such as secure boot chain, virtualization or secure communication interfaces. |
| III.I.15 | Application specific integrated circuits (ASIC) and field-programmable gate arrays (FPGA) with security-related functionalities | Application specific integrated circuits (ASIC) with security-related functionalities are products with digital elements that are integrated circuits, fully or partially custom-designed to perform a specific function or implement a specific application, including microcode and other low-level firmware. They additionally provide security-related functionalities, such as encryption, authentication, secure key storage, random number generation, trusted execution environment, or other hardware-based protection mechanisms, that aim to secure other products, networks or services beyond the ASIC itself, such as secure boot chain, virtualization or secure communication interfaces. Field-programmable gate arrays (FPGA) with security-related functionalities are products with digital elements that are integrated circuits characterized by a matrix of configurable logic blocks designed to be reprogrammable after manufacturing to perform a specific function or implement a specific application, including microcode and other low-level firmware. They additionally provide security-related functionalities, such as encryption, authentication, secure key storage, random number generation, trusted execution environment, or other hardware-based protection mechanisms, that aim to secure other products, networks or services beyond the FPGA itself, such as secure boot chain, virtualization or secure communication interfaces. |
| III.I.16 | Smart home general purpose virtual assistants | Products with digital elements that communicate on the public Internet, whether directly or via other equipment, that process demands, tasks or questions based on natural language prompts, such as through audio or written input, and that, based on those demands, tasks or questions, provide access to other services or control the functions of connected devices in residential settings. This category includes but is not limited to smart speakers with an integrated virtual assistant, and standalone virtual assistants that meet this description. |
| III.I.17 | Smart home products with security functionalities, including smart door locks, security cameras, baby monitoring systems and alarm systems | Products with digital elements that protect the physical security of consumers in a residential setting and which can be controlled or managed remotely from other systems, as well as hardware and software that centrally control such products. This category includes but is not limited to smart door locking devices, baby monitoring systems, alarm systems and home security cameras. |
| III.I.18 | Internet connected toys covered by Directive 2009/48/EC of the European Parliament and of the Council ( 1 ) that have social interactive features (e.g. speaking or filming) or that have location tracking features | Internet connected toys that have social interactive features are products with digital elements that are covered by Directive 2009/48/EC, that communicate on the public Internet, whether directly or via any other equipment, and that have embedded technologies that enable inbound and outbound communication, such as keyboard, microphone, speaker or camera. Internet connected toys that have location tracking features are products with digital elements that are covered by Directive 2009/48/EC, that communicate on the public Internet, whether directly or via any other equipment, and that have technologies that enable tracking or inferring of the geographical location of the toy or its user. Where the toy merely detects the proximity of the user or of other toys by using sensing technologies, the toy is not to be considered to have location tracking features. |
| III.I.19 | Personal wearable products to be worn or placed on a human body that have a health monitoring (such as tracking) purpose and to which Regulation (EU) 2017/745 ( 2 ) or (EU) 2017/746 of the European Parliament and of the Council ( 3 ) do not apply, or personal wearable products that are intended for the use by and for children | Personal wearable products to be worn or placed on a human body that have a health monitoring purpose are products with digital elements that are worn on the body directly or via clothing or accessories and that can, regularly or continuously, sense and further process information, including body metrics, relevant to the user’s health, excluding products that fall within the scope of Regulation (EU) 2017/745 or of Regulation (EU) 2017/746. This category includes but is not limited to fitness trackers, smartwatches, smart jewellery, smart clothing and sports apparel that meet this description. Personal wearable products that are intended for the use by and for children are products with digital elements which can be worn or placed on the body, directly or via clothing or accessories, of individuals under the age of 14. This category includes but is not limited to child safety wearables. |
| III.II.1 | Hypervisors and container runtime systems that support virtualised execution of operating systems and similar environments | Hypervisors are software products with digital elements that abstract and/or allocate computing resources and enable the execution, management and orchestration of virtual machines that are logically separated from each other and/or from the physical hardware. Hypervisors may run directly on hardware (bare metal), on top of an operating system, or within another virtual machine (nested virtualisation). In the context of this category of products, a virtual machine is a software-defined logical separation of a computing environment, which includes a virtualised set of hardware resources (e.g. CPU, memory, storage, network interfaces) and typically hosts its own operating system. This category includes but is not limited to type 1 hypervisors (bare metal), type 2 hypervisors (hosted on an operating system) and hybrid hypervisors. Container runtime systems are software products with digital elements that manage the execution and lifecycle of containers running on a single host operating system as isolated processes, allocating resources and allowing the management and orchestration of individual containers. In the context of this category of products, a container is a software-based execution environment that encapsulates one or more software components and their dependencies in a single package, enabling it to run independently and consistently. |
| III.II.2 | Firewalls, intrusion detection and prevention systems | Firewalls are products with digital elements that protect a connected network or system from unauthorized access by monitoring and restricting data communication traffic to and from that network. This category includes but is not limited to network firewalls and application firewalls such as web application firewalls or filters and anti-spam gateways. Intrusion detection systems are products with digital elements that monitor traffic once it has entered the network environment for suspicious activity and detect or identify that an intrusion has been attempted, is occurring, or has occurred on a connected network or system. This category includes but is not limited to network-based intrusion detection systems and host-based intrusion detection systems. Intrusion prevention systems are products with digital elements composed of an intrusion detection system that actively responds to an intrusion to a connected network or system. This category includes but is not limited to network-based intrusion prevention systems and host-based intrusion prevention systems. |
| III.II.3 | Tamper-resistant microprocessors | Products with digital elements that are microprocessors with security-related functionalities referred to in Table ‘Class I’, point 13, of this Annex, including tamper evidence, resistance or response, and which additionally are designed to provide protection of AVA_VAN level 2 or 3, as set out in the Common Criteria and the Common Evaluation Methodology. |
| III.II.4 | Tamper-resistant microcontrollers | Products with digital elements that are microcontrollers with security-related functionalities referred to in Table ‘Class I’, point 14, of this Annex, including tamper evidence, resistance or response, and which additionally are designed to provide protection of AVA_VAN level 2 or 3, as set out in the Common Criteria and the Common Evaluation Methodology. |
| IV.1 | Hardware Devices with Security Boxes | Hardware products with digital elements that securely store, process, or manage sensitive data or perform cryptographic operations, and that consist of multiple discrete components, incorporating a hardware physical envelope providing tamper evidence, resistance or response as countermeasures against physical attacks. This category includes but is not limited to physical payment terminals, hardware security modules that generate and manage cryptographic elements, and tachographs that meet the above description. |
| IV.2 | Smart meter gateways within smart metering systems as defined in Article 2(23) of Directive (EU) 2019/944 of the European Parliament and of the Council ( 1 ) and other devices for advanced security purposes, including for secure cryptoprocessing | Smart meter gateways are products with digital elements that control communication between components in or connected to smart metering systems as defined in Article 2(23) of Directive (EU) 2019/944, and authorised third parties, such as utility providers. Smart meter gateways collect, process and store meter or personal data, protect data and information flows by supporting specific cryptographic needs, such as encryption and decryption of data, incorporate firewalling functionalities and provide the means to control other devices. This category includes but is not limited to smart meter gateways related to smart metering systems measuring electricity as defined in Article 2(23) of Directive (EU) 2019/944. It may also include smart meter gateways used in other smart metering systems measuring consumption of other sources of energy such as gas or heat, provided that the gateway meets this description. |
| IV.3 | Smartcards or similar devices, including secure elements | Secure elements are microcontrollers or microprocessors with security-related functionalities, including tamper evidence, resistance or response. They typically store, process, or manage cryptographic operations or sensitive data, such as identity credentials or payment credentials. Secure elements are designed to provide protection of at least AVA_VAN.4, as set out in the Common Criteria or the Common Evaluation Methodology. They can be discrete silicon or can be integrated into systems on chip (SoC). Secure elements can incorporate an application environment or an operating system, and can include one or more applications. This category includes but is not limited to Trusted Platform Modules (TPMs) and embedded Universal Integrated Circuit Card (UICC). Smartcards or similar devices are secure elements integrated into a carrier material, such as plastic or wood, in the shape of a card, or secure elements integrated into carrier materials taking other shapes. This category includes but is not limited to identity and travel documents, qualified signature cards, replaceable UICCs, physical payment cards, physical access cards, digital tachograph cards or wrist bands with integrated payment secure elements. |
What to record
For each product you place on the market: the core functionality in one sentence, in the words of the description it matches or the statement that it matches none; the ancillary functions you set aside under rule 1; the components you integrate that are themselves listed, set aside under rule 2; where the product resembles a category, whether it exceeds or falls short and why, under rule 3; and, for a suite, which modules are sold separately. That page is the classification a notified body will ask for, the input to the scope determination, which now shows the description under each category, and the reason your technical file names one conformity procedure and not another.
Sources
- Regulation (EU) 2024/2847, Article 7(1) and (4), Article 8(1), Article 32, Article 64(3), Annex III, Annex IV, Annex VII.
- Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025, recitals 1 to 5, Articles 1 to 3, Annex I and Annex II, read from the Publications Office on 12 September 2026.
- European Commission, Commission guidance on the application of Regulation (EU) 2024/2847, C(2026) 5252 final of 27 July 2026, Annex, section 6, paragraphs 136 to 152 and examples 57 to 63.
This is not legal advice. The descriptions are the law's own words and the guidance's examples are the Commission's; the classification of your product is yours, and it is the first thing a market surveillance authority will read.