Join our Newsletter — 33% off our NHI Course
Home› Guides› EU CRA Product Classes Guide: Important, Critical and…
Guide Regulations & Frameworks

EU CRA Product Classes Guide: Important, Critical and Default Products and Conformity Routes

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Under the EU Cyber Resilience Act, the category a product falls into decides whether a manufacturer can self-assess or must pay a notified body, and getting that call wrong can block a product from the EU market. This guide explains the default, important (class I and class II) and critical categories of Regulation (EU) 2024/2847, the technical descriptions fixed by Commission Implementing Regulation (EU) 2025/2392, and the conformity assessment routes each category allows. It is written for product security leads, compliance managers and engineering owners who must classify a portfolio before the main obligations apply on 11 December 2027. Status checked on 27 October 2026 against EUR-Lex and the Commission's CRA pages. It does not repeat the overview of the whole Regulation: see the EU Cyber Resilience Act Guide.

Key takeaways

  • Most products are default category and the manufacturer may demonstrate conformity by internal control (module A), whatever technical specification it uses.
  • Class I important products can use self-assessment only where the manufacturer applies harmonised standards, common specifications or a suitable European cybersecurity certification; otherwise a notified body is needed.
  • Class II important products always need a third party, even when harmonised standards are applied: hypervisors, container runtimes, firewalls, IDS/IPS and tamper-resistant microprocessors and microcontrollers.
  • Critical products sit at the top: hardware devices with security boxes, smart meter gateways and smartcards or secure elements, where European certification at assurance level at least "substantial" may be required.
  • Classification follows core functionality of the product as a whole, not the components inside it, so embedding a class I component does not make the whole product class I.

Scope: who and what is covered

The CRA applies to products with digital elements made available on the EU market, hardware and software, including components placed on the market separately, where the product is connected directly or indirectly to another device or network. Products already covered by sector rules, such as medical devices, aviation and motor vehicles, are excluded, as is certain free and open-source software that is not supplied in the course of a commercial activity. The classification question in this guide only arises for products that are in scope.

Classification duties sit with the manufacturer, the entity that places the product on the market under its own name or trademark. Importers and distributors rely on the manufacturer's choice of procedure and the EU declaration of conformity, but they should check that a notified body certificate exists where the category requires one.

The four categories at a glance

CategoryWhere definedExamples given by the CommissionThird party needed?
DefaultEverything in scope not listed in Annex III or IVMemory chips, mobile apps, smart speakers, computer gamesNo, self-assessment allowed
Important, class IAnnex III, class I (19 categories)Operating systems, browsers, password managers, VPNs, routers, SIEMOnly if harmonised standards or equivalent are not applied in full
Important, class IIAnnex III, class II (4 categories)Hypervisors, container runtimes, firewalls, IDS/IPSYes, always
CriticalAnnex IV (3 categories)Smart cards, secure elements, smart meter gateways, HSMsYes, notified body or European certification

Key obligations

Every manufacturer, whatever the category, must meet the essential cybersecurity requirements, carry out and document a cybersecurity risk assessment, prepare technical documentation, draw up the EU declaration of conformity and affix the CE marking. Implementing Regulation (EU) 2025/2392 restates that this risk assessment applies whether or not the product is important or critical (recital 6). What changes with category is the conformity assessment procedure in Article 32 and the procedures in Annex VIII.

Conformity routes by category

CategoryModule A internal controlModule B + C (EU-type examination plus conformity to type)Module H (full quality assurance)European cybersecurity certification
DefaultAllowedAllowed (voluntary)Allowed (voluntary)Voluntary
Class IOnly with harmonised standards, common specifications or certification appliedAllowedAllowedAllowed where a suitable scheme exists
Class IINot allowed (FOSS exception below)AllowedAllowedAllowed where a suitable scheme exists
CriticalNot allowedAllowed unless certification is mandatedAllowed unless certification is mandatedCan be made mandatory by delegated act, assurance at least "substantial"

Recital 91 of the Regulation explains the logic: internal control (module A) for most products, modules B, C or H for important products, and a third party always for class II "even where harmonised standards are applied". It also sets an exception: important products that qualify as free and open-source software may use module A where the technical documentation is made public.

The class I and class II lists

Implementing Regulation (EU) 2025/2392 gives a technical description of each category. The class I list covers:

  • Identity and access: identity management systems and privileged access management software and hardware, including authentication and access control readers and biometric readers; password managers; PKI and digital certificate issuance software.
  • Network and security software: standalone and embedded browsers; anti-malware software; VPN products; network management systems; SIEM systems; physical and virtual network interfaces; routers, internet modems and switches.
  • Platform and silicon: boot managers (including UEFI firmware and boot loaders); operating systems; microprocessors, microcontrollers, ASICs and FPGAs with security-related functionalities.
  • Consumer devices: smart home general-purpose virtual assistants; smart home security products such as smart door locks, security cameras, baby monitors and alarm systems; internet-connected toys with social interactive features or location tracking; personal wearables that monitor health and are outside the medical device rules, or wearables intended for children under 14.

Class II has four categories: hypervisors and container runtime systems; firewalls, intrusion detection and intrusion prevention systems; tamper-resistant microprocessors; and tamper-resistant microcontrollers, the last two being the class I items with tamper protection designed to Common Criteria AVA_VAN level 2 or 3.

Annex IV critical products are hardware devices with security boxes (the Implementing Regulation gives payment terminals, hardware security modules and tachographs as examples), smart meter gateways and other advanced security devices, and smartcards or similar devices including secure elements designed to at least AVA_VAN.4, such as TPMs, UICCs and identity documents.

How the core functionality test works

  • Whole product: the procedures apply only if the product as a whole is important or critical. Integrating a component that falls into a category does not by itself trigger the stricter procedure, but the manufacturer must still assess that component's security as part of the whole product (recital 3 of 2025/2392).
  • Core, not incidental: extra functions do not take a product out of a category, and overlapping functions do not bring it in. A smart TV with a browser is not a class I browser product because browsing is not its core function; a browser sold as a product is.
  • Assurance language: AVA_VAN levels may be expressed using the latest or older versions of the Common Criteria and Common Evaluation Methodology (recital 8). See the Common Criteria Evaluation Guide.

Timeline and current status

Status as checked on 27 October 2026 on the Commission's CRA implementation page. Dates marked as quarters were plans when checked and may move.

DateMilestoneEffect on classification work
23 Oct 2024Regulation (EU) 2024/2847 adoptedAnnex III and IV lists fixed
10 Dec 2024Entry into forceCommission's delegated power to update the annexes runs for five years from this date
28 Nov 2025Implementing Regulation (EU) 2025/2392 adopted (OJ 1 Dec 2025)Technical descriptions of each important and critical category
11 Jun 2026Provisions on notifying conformity assessment bodies applyMember States designate notifying authorities; bodies can seek notification
27 Jul 2026Commission guidance C(2026) 5252 published (non-binding)Scope, substantial modification, support periods, risk assessment examples
11 Sep 2026Reporting obligations applyApplies to all categories, see the EU Cyber Resilience Act Vulnerability and Incident Reporting Guide
Q3 2026 and 30 Oct 2027Standardisation deliverables plannedHarmonised standards decide whether class I can self-assess
Q4 2026Delegated act on presumption of conformity for EUCC plannedCertification route for class I, class II and critical products
11 Dec 2026Target for sufficient notified bodies across Member StatesCapacity for class II and critical assessments
11 Dec 2027Full applicationProducts placed on the market must carry valid CE marking under the CRA

The practical risk is timing. Harmonised standards were still being delivered when checked, so a class I manufacturer cannot yet be sure that a standard will be cited in time for 11 December 2027. Plan for a notified body slot as a fallback.

Enforcement and penalties

Market surveillance authorities in each Member State enforce the CRA. A product that carries the CE marking under the wrong procedure, for example a class II firewall self-assessed under module A, has no valid conformity assessment and can be subject to corrective action, restriction or withdrawal. Article 64 requires Member States to lay down rules on penalties and sets maximum administrative fines; read the Article 64 text on EUR-Lex for the tiers that apply to your breach type, because this guide does not restate the amounts. Recital 120 notes that fines should not be imposed on microenterprises or small enterprises for failing to meet the 24-hour early warning deadline. See the Product Security Laws Map for how other regimes compare.

What it means for AI agents and non-human identities

Several class I categories are identity products in their own right. Identity management systems, privileged access management, password managers and PKI or certificate issuance software are all listed, so a vendor that sells a secrets vault, a machine identity platform or a certificate lifecycle tool as a product should test its core functionality against those descriptions first. See the Machine Identity, PKI and Certificate Lifecycle Guide.

  • Agent platforms: an AI agent framework is not a listed category, so it is usually default unless its core function is identity management, network security or virtualisation. A product whose core is an agent sandbox built on a container runtime should be checked against class II.
  • Machine credentials in the product: the essential requirements on protection against unauthorised access apply in every category, so hardcoded keys, shared device credentials and long-lived update tokens are a conformity issue even for default products. See the Non-Human Identity (NHI) Guide.
  • Signing keys: update signing keys and boot chain keys protect the integrity requirements; a stolen key undermines conformity across the installed base, as the MSI signing keys leak showed for firmware.

Compliance steps

  1. Inventory products and versions: list every product with digital elements you place on the EU market, including separately sold components and software.
  2. Write a one-line core function statement for each product, in the wording a market surveillance authority would use, before reading the annexes.
  3. Test against the 2025/2392 descriptions: compare the core function to each class I, class II and critical description; record the reasoning and the paragraph matched, including why near-miss categories do not apply.
  4. Peer review borderline calls: have legal and product security sign off on any product where a core function overlaps a listed category, such as a router with integrated firewall or a gateway with VPN.
  5. Choose the procedure: default products pick module A; class I products decide early whether to rely on harmonised standards (track their citation) or book a notified body; class II and critical products book module B + C or module H, or certification.
  6. Engage notified bodies early: check NANDO for bodies notified under the CRA and agree scope and lead times; capacity was still being built when checked.
  7. Build the technical file once: risk assessment, SBOM, vulnerability handling process and test evidence serve every route. See the SBOM Guide and the PSIRT Guide.
  8. Re-test on change: a substantial modification or a new core function can move a product into a new category; add a classification check to the release gate.

Decision guidance

  • Class I with standards versus notified body: self-assessment against harmonised standards is cheaper and faster but depends on standards being cited in time and applied in full; partial application puts you back on the third-party route.
  • Module B + C versus module H: B + C examines a product type and suits a few stable product lines; H approves the manufacturer's quality system and suits large portfolios with frequent releases.
  • Small manufacturers: the Commission guidance gives particular attention to microenterprises and SMEs; a small firm with one class II product should budget the notified body fee and timeline as a launch dependency.
  • Large portfolios: keep a classification register with owners and review dates, and align it with the product catalogue so new SKUs cannot ship unclassified.

Common failure patterns

  • Classifying by component: treating a product as class I because it contains a microcontroller with security features, when the whole-product rule says otherwise.
  • Classifying by marketing name: calling a firewall a "security gateway" does not change its core function or move it out of class II.
  • Assuming standards will exist: planning module A for class I without a cited harmonised standard and no notified body fallback.
  • Ignoring identity products: vault, PAM and certificate tool vendors assuming they are default because they sell software.
  • No evidence of reasoning: a correct classification without a written rationale is hard to defend in a market surveillance inquiry.
  • Weak update key protection: signing keys stored without HSM controls, which puts the integrity requirements of every shipped unit at risk.

Detection and measurement

  • Coverage: percentage of EU-marketed products with a recorded category and rationale (target 100% well before 11 December 2027).
  • Borderline review: number of products with a documented legal and security sign-off on near-miss categories.
  • Notified body readiness: class II and critical products with a confirmed notified body slot.
  • Standards tracking: class I products mapped to a named draft or cited harmonised standard.
  • Change control: releases that passed the classification gate versus releases shipped without it.

Framework mapping

CRA activityNIST CSF 2.0ISO/IEC 27001:2022 Annex ANIST SP 800-53 r5
Product inventory and classificationID.AM (Asset Management)A.5.9 Inventory of information and other associated assetsCM-8 System Component Inventory
Risk assessment per productID.RA (Risk Assessment)A.5.8 Information security in project managementRA-3 Risk Assessment
Secure development and testing evidencePR.PS (Platform Security)A.8.25 Secure development life cycleSA-11 Developer Testing and Evaluation
Third-party assessment and certificationGV.SC (Cybersecurity Supply Chain Risk Management)A.5.36 Compliance with policies, rules and standardsCA-2 Control Assessments

Practitioner checklist

  • Every EU-marketed product has a written core function statement and a recorded category.
  • Each classification cites the matching paragraph of Implementing Regulation (EU) 2025/2392, or states why none matches.
  • Identity, PAM, password manager and PKI products have been checked against class I explicitly.
  • Class II and critical products have a notified body or certification route agreed.
  • Class I products relying on self-assessment are mapped to a harmonised standard with a fallback plan.
  • Open-source important products using module A publish their technical documentation.
  • A classification check sits in the release gate for new features and substantial modifications.
  • Signing keys and device credentials are covered in the risk assessment for every category.

Standards and references

Related NHI Mgmt Group resources: EU Cyber Resilience Act Guide · EU Cybersecurity Certification EUCC Guide · Product Security Laws Map. This guide summarises the product classification and conformity assessment rules of Regulation (EU) 2024/2847 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.