Product team testing a smart-speaker-style device with microphones in an anechoic chamber

Cyber Resilience Act

CRA Annex III and IV: important and critical products with digital elements, explained

Last updated:

Not every product under the Cyber Resilience Act faces the same compliance route: Annex III lists 19 Class I categories and 4 stricter Class II categories of "important" products, while Annex IV lists just 3 categories of "critical" products facing the toughest conformity route of all. Most products fall outside these lists, into a default tier that can self-assess against Annex I. But if a product's core functionality matches one of the Annex III categories, it is an important product with digital elements (split into Class I and the stricter Class II); if it matches one of the three Annex IV categories, it is a critical product with digital elements. Getting this classification right matters because it decides whether you can self-assess, need a notified body, or need a formal EU cybersecurity certificate.

The category lists and article references below were checked on 10 November 2026 against the Official Journal texts of Regulation (EU) 2024/2847 and Implementing Regulation (EU) 2025/2392, and against the Commission's FAQs on the CRA (version 1.4). The FAQ answers further down keep their original wording.

Key takeaways

  • Article 7(1) sets the basic test: a product is classified by its own core functionality, not by what it contains.
  • The conformity assessment guide walks through each route step by step.
  • Annex III and IV name categories in plain language, but plenty of products sit near a boundary — does a smartphone's built-in password manager make the phone an "important product"?
  • Several Implementing Regulation 2025/2392 descriptions reach further into embedded hardware and firmware than the short category names suggest.

What are the three tiers, and what does the Article 7(1) rule say?

Article 7(1) sets the basic test: a product is classified by its own core functionality, not by what it contains. A VPN feature bundled into a broader business application does not turn that whole application into an "important" VPN product — only a product whose core purpose is to provide VPN functionality falls under that Annex III category. The same logic applies throughout: integrating an important or critical component into a larger product does not, by itself, pull the larger product into that stricter tier.

Article 7(2) gives the two criteria a category must meet to belong in Annex III at all: (a) the product primarily performs functions critical to the cybersecurity of other products, networks or services — securing authentication and access, intrusion prevention and detection, endpoint security, or network protection; or (b) it performs a function carrying a significant risk of adverse effects through direct manipulation, such as a central system function like network management, configuration control, virtualisation, or processing of personal data. Article 8 layers on extra criteria for critical products in Annex IV, including whether essential entities under the NIS2 Directive depend on the product and whether it risks disrupting critical supply chains.

Classification changes the conformity route, not the work itself. The Commission's FAQs on the CRA (entry 3.3) stresses that every manufacturer, default, important or critical, carries out a full cybersecurity risk assessment and implements Annex I in proportion to the risks. Back to the Cyber Resilience Act hub.

Which 19 categories are in Annex III Class I?

Per the regulation's own Annex III text, Class I covers:

  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 digital elements with the function of 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. Application-specific integrated circuits (ASICs) and field-programmable gate arrays (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 with social-interactive features or location-tracking features
  19. Personal wearable products with a health-monitoring purpose, or that are intended for use by children, where Regulation (EU) 2017/745 or (EU) 2017/746 (the medical devices regulations) do not already apply

What is in Annex III Class II and Annex IV?

Class II, reserved for important products the recitals describe as carrying greater potential impact if compromised, lists 4 categories: hypervisors and container runtime systems that support virtualised execution of operating systems and similar environments; firewalls and intrusion detection/prevention systems; tamper-resistant microprocessors; and tamper-resistant microcontrollers.

Annex IV, the critical tier, is the shortest list of all — just 3 categories: hardware devices with security boxes; smart meter gateways within smart metering systems and other devices for advanced security purposes, including secure cryptoprocessing; and smartcards or similar devices, including secure elements.

Tier Example categories Default conformity route
Default (not in Annex III/IV) Most products with digital elements Module A: manufacturer self-assessment
Important, Class I Browsers, password managers, VPN products, routers/modems/switches, smart home security devices Module A only if fully applying harmonised standards/common specifications/a certification scheme at "substantial"; otherwise Module B+C or H with a notified body
Important, Class II Hypervisors, firewalls/IDS/IPS, tamper-resistant microprocessors/microcontrollers Always third-party: Module B+C, Module H, or a certification scheme at "substantial"
Critical (Annex IV) Hardware security modules, smart meter gateways, smartcards/secure elements A European cybersecurity certificate at least "substantial" where the Commission requires one by delegated act under Article 8(1); otherwise the Class II routes — see our guide to the EUCC, one scheme that can fill that role

The conformity assessment guide walks through each route step by step.

Where do the exact boundaries come from?

Annex III and IV name categories in plain language, but plenty of products sit near a boundary — does a smartphone's built-in password manager make the phone an "important product"? Article 7(4) required the Commission to settle questions like that by adopting an implementing act with precise technical descriptions, due 11 December 2025. The Commission met that deadline on 28 November 2025, adopting Commission Implementing Regulation (EU) 2025/2392; it was published in the Official Journal on 1 December 2025 and has applied since 21 December 2025. Its own Annex I gives the technical descriptions for important-product categories and its Annex II for critical-product categories — manufacturers near a classification boundary should check that text, not just the category names in Annex III/IV themselves. Its recital 7 adds that the examples it gives are illustrative, not exhaustive.

The lists can also move. Under Article 7(3) and Article 8(2) of the CRA the Commission can amend Annex III or IV by delegated act — adding a category, moving one between Class I and Class II, or withdrawing one — with a transitional period that is generally at least 12 months for Annex III changes and six months for Annex IV changes.

How do the technical descriptions read for embedded products?

Several Implementing Regulation 2025/2392 descriptions reach further into embedded hardware and firmware than the short category names suggest. The rows below quote what each description includes and give a device maker's reading.

Category (tier) What the technical description includes Device maker's reading
Operating systems (Class I) Real-time, general-purpose and special-purpose operating systems An RTOS sold as a product is in scope of this category; a device that merely runs one is classified by its own core function
Boot managers (Class I) UEFI firmware, single-stage and multi-stage boot loaders A bootloader you sell separately is Class I; one built into your device firmware follows the device
Physical and virtual network interfaces (Class I) Wired and wireless interface cards, controllers and adapters, such as Wi-Fi, Ethernet, USB, Bluetooth, Zigbee or fieldbus Wi-Fi or Bluetooth modules sold to integrators are likely to fall here for the module maker
Routers, modems, switches (Class I) Wired and wireless routers, cellular and DSL modems, managed switches and bridges such as wireless access points Access points and cellular modems are named explicitly
Microcontrollers with security-related functionalities (Class I) Security functions such as encryption, secure key storage, random number generation or a trusted execution environment that secure other products Many connected-device MCUs advertise these features; the chip maker classifies the chip
Tamper-resistant microcontrollers (Class II) Class I security MCUs that also have tamper evidence, resistance or response and are designed for protection at Common Criteria AVA_VAN level 2 or 3 The AVA_VAN design target separates Class I from Class II
Smartcards or similar devices, including secure elements (Annex IV) Secure elements designed for at least AVA_VAN.4, including TPMs and embedded UICCs A discrete TPM or eSIM chip is a critical product for its maker
Hardware devices with security boxes (Annex IV) Physical payment terminals, hardware security modules and tachographs built from several components inside a physical envelope with tamper evidence, resistance or response A payment terminal that meets this description is a critical product
Smart meter gateways (Annex IV) Gateways for electricity smart metering, and gateways for gas or heat metering that meet the description Utility gateway makers should read this row closely

Recital 8 explains the AVA_VAN approach: it is a standardised Common Criteria way to express how much resistance against exploitation a chip is designed for.

Does integrating a classified component make your device important or critical?

No, not by itself; the device's own core functionality decides. Recitals 3 to 5 of the Implementing Regulation and the Commission FAQ (3.2 and 3.4) give the reference examples:

  • Secure element in a laptop. Integrating it does not make the laptop subject to the procedure for "smartcards and similar devices, including secure elements" (FAQ 3.2).
  • Embedded browser in a news app. The app is not a browser product (recital 3).
  • Router with a built-in firewall. It still has the core functionality of a router, which is Class I; the firewall feature does not move it to Class II (recital 4).
  • Smartphone with an OS and a password manager. Its core functionality is neither, so it is generally not classified as either (FAQ 3.4).
  • SOAR software that can do SIEM tasks. Not a SIEM, because its core functionality differs (recital 5).

You still answer for the whole product. Recital 3 says the manufacturer must show the product as a whole meets Annex I, taking account of the security of the integrated component; see CRA Annex I explained.

Worked example: how would four sample devices be classified?

The products below are hypothetical and synthetic, not customer cases. The classification is a first reading for discussion; the final call rests on the full technical descriptions and your own documentation.

Sample product Core functionality First reading Route consequence
Wi-Fi video doorbell with app Home security camera Class I, Annex III point 17 Module A only with full harmonised-standard coverage; otherwise a notified body
Industrial Ethernet switch with web management Switch with a management plane Class I, Annex III point 12 As above
Bluetooth temperature logger for cold-chain transport Sensing and logging Default Module A available
Payment terminal for retail Hardware device with a tamper-resistant security envelope Annex IV point 1 Certification where required by delegated act; otherwise Class II routes

Two of the four land in Class I without any "security product" in their marketing, which is why classification belongs at the start of a project, not at the end.

What are the common classification pitfalls?

  • Reading only the Annex III names. The 2025/2392 descriptions add explicit examples such as wireless access points, cellular modems, UEFI firmware and tachographs.
  • Classifying by bill of materials. A TPM, secure element or certified MCU inside your device does not make the device critical or important (Article 7(1), FAQ 3.2).
  • Assuming extra functions remove a category. An operating system that ships a calculator is still an operating system (recital 4).
  • Confusing a smart speaker with a virtual assistant. The Commission lists smart speakers as a default example, while Class I point 16 covers smart home general-purpose virtual assistants, including smart speakers with an integrated assistant. Check which one you sell.
  • Ignoring the age limit for wearables. Point 19 covers wearables intended for children, which 2025/2392 defines as under 14.

What is a workable starting point?

  1. Check core functionality first, not component inventoryArticle 7(1)'s rule means you classify by what your product's core purpose is, not by every security-relevant library or feature it happens to bundle.
  2. Read Implementing Regulation (EU) 2025/2392 before assuming a category appliesThe technical descriptions in its own Annex I/II, not the short Annex III/IV category names, are what actually settle edge cases.
  3. Plan for a notified body early if you land in Class II or Annex IVUnlike default or most Class I products, these routes require third-party involvement; notified-body capacity and lead times are a real planning constraint, not a formality.
  4. Track harmonised standards if you land in Class ISelf-assessment depends on them; see CRA harmonised standards for the M/606 status.
  5. Revisit your classification when the Commission amends Annex III/IVThe delegated-act mechanism means today's "default" product could later be added to Annex III — don't treat this as a one-time check.

SoftWSP's firmware security work can help work out whether your product falls under Annex III or IV and what that means for your conformity assessment route: see Device & Firmware Security.

This guide summarises Regulation (EU) 2024/2847 and Commission Implementing Regulation (EU) 2025/2392; it is not a substitute for the regulations' own text on EUR-Lex or for legal advice; a conformity assessment's classification decision rests on that current official text, not on this summary.

Put this guide to work

Frequently asked questions

What is the difference between a 'default', 'important' and 'critical' product under the CRA?

The Cyber Resilience Act (Regulation (EU) 2024/2847) sorts products with digital elements into three conformity-assessment tiers. Most products are 'default': the manufacturer can self-assess against Annex I (Module A, internal control). A product whose core functionality matches one of the categories listed in Annex III is 'important', split into Class I and Class II. A product whose core functionality matches one of the three categories in Annex IV is 'critical'. Per Article 7(1), only a product's own core functionality triggers reclassification — integrating a component that has important-product functionality (for example, a VPN feature inside a larger business application) does not by itself make the whole product 'important'.

What products are in Annex III Class I and Class II?

Annex III Class I lists 19 categories, including identity management and privileged access management software/hardware, standalone and embedded browsers, password managers, anti-malware software, VPN products, network management systems, SIEM systems, boot managers, PKI and digital-certificate-issuance software, physical and virtual network interfaces, operating systems, routers/modems/switches for internet connection, security-related microprocessors and microcontrollers, security-related ASICs/FPGAs, smart home virtual assistants, smart home security products (smart locks, security cameras, baby monitors, alarms), internet-connected toys with interactive or location-tracking features, and child-use or health-monitoring wearables. Annex III Class II lists 4 categories considered higher-risk: hypervisors and container runtime systems, firewalls/intrusion detection and prevention systems, and tamper-resistant microprocessors and microcontrollers.

What makes a product 'critical' under Annex IV, and how is that different from 'important'?

Annex IV lists only three categories: hardware devices with security boxes (hardware security modules), smart meter gateways and other devices for advanced security purposes including secure cryptoprocessing, and smartcards or similar devices including secure elements. Under Article 8, critical products face the strictest route: the Commission may require a European cybersecurity certificate at an assurance level of at least 'substantial' under an EU scheme such as the EUCC, rather than the self-assessment or notified-body options available to most important products.

Where are the exact technical boundaries of each Annex III/IV category defined?

Article 7(4) required the Commission to adopt, by 11 December 2025, an implementing act giving precise technical descriptions of the Annex III and IV categories. The Commission adopted that act, Commission Implementing Regulation (EU) 2025/2392, on 28 November 2025; it was published in the Official Journal on 1 December 2025 and has applied since 21 December 2025. It sets out the technical descriptions in its own Annex I (important products) and Annex II (critical products) and is the instrument to check for edge cases — for example, whether a given device's security feature is incidental or core to its function.

Sources

  1. Regulation (EU) 2024/2847 (Cyber Resilience Act), Articles 7, 8 and 32, and Annexes III and IV, Official Journal text, EUR-Lex
  2. 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, EUR-Lex
  3. European Commission: Cyber Resilience Act, summary of the legal text
  4. InsideCRA: Annex III — Important products with digital elements (article-by-article CRA reference reproducing the regulation's annex text)
  5. InsideCRA: Annex IV — Critical products with digital elements
  6. TÜV: Commission Implementing Regulation (EU) 2025/2392 on the technical description of important and critical product categories
  7. European Commission: Cyber Resilience Act – Conformity assessment (last update 31 July 2026)
  8. European Commission: FAQs on the Cyber Resilience Act, version 1.4 (4 September 2026)
Was this guide helpful?

In this cluster

CRA Annex III and IV: important and critical products with digital elements, explained