FAQEUCyber Resilience Act

EU Cyber Resilience Act FAQ Important and Critical Products

Use this CRA FAQ to classify important and critical products with digital elements, understand the role of core functionality, and choose the right conformity assessment route.

Built for product, legal, certification, and compliance teams mapping products against CRA Annex III, Annex IV, and the Commission technical descriptions.

Author
Sorena AI
Published
Mar 10, 2026
Updated
Mar 10, 2026
Questions
13

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published Mar 10, 2026
Updated Mar 10, 2026
Overview

The CRA does not treat every product with digital elements the same way for conformity assessment. Products whose core functionality matches an Annex III category are important products, divided into class I and class II. Products whose core functionality matches an Annex IV category are critical products. This FAQ explains how to classify a product, what sources to use, and how classification changes the conformity route without creating a separate set of cybersecurity requirements.

Search this module

Find a question or answer quickly

13 of 13 questions
Question 1

What are important products with digital elements under the CRA?

Important products are products with digital elements whose core functionality matches a product category in CRA Annex III.

Annex III is split into class I and class II. The class matters because it changes the conformity assessment route under Article 32. Class I can sometimes use internal control, while class II must use one of the stricter Article 32(3) routes.

Citations
Cyber Resilience Act

Article 7(1) defines important products by core functionality matching Annex III; Annex III divides them into class I and class II.

European Commission CRA FAQs

Section 3.1 confirms that manufacturers should look at core functionality to decide whether a product is important or critical.

Recommended next step

Classify CRA important and critical products with cited evidence

Research Copilot helps CRA teams map core functionality to Annex III, Annex IV, and Implementing Regulation (EU) 2025/2392, then connect the result to the right conformity assessment route.

Question 2

What are critical products with digital elements under the CRA?

Critical products are products with digital elements whose core functionality matches a product category in CRA Annex IV.

Annex IV is narrower than Annex III. It currently identifies critical categories such as hardware devices with security boxes, smart meter gateways and other advanced-security devices, and smartcards or similar devices including secure elements. For classification work, teams should still use the official Annex IV text and the technical descriptions in Commission Implementing Regulation (EU) 2025/2392 rather than relying on product labels alone.

Citations
Cyber Resilience Act

Article 8(1) and Annex IV define critical products by core functionality matching an Annex IV category.

Question 3

How should a manufacturer decide whether a product is important or critical?

Start with the product's core functionality: the main features and technical capabilities without which the product would not meet its intended purpose.

Then compare those features and capabilities with the CRA Annex III or Annex IV category and the corresponding technical description in Implementing Regulation (EU) 2025/2392. Marketing category names, deployment environment, and partial feature overlap are not enough on their own.

Citations
Question 4

Does a product become important or critical just because it includes an important or critical component?

No. The CRA says that integrating a product with the core functionality of an Annex III category does not by itself make the larger product subject to the important-product conformity routes.

The Commission FAQ applies the same practical logic to integrated important or critical components. A news app with an embedded browser, a laptop with a secure element, or a product that integrates an operating system still has to be classified by the core functionality of the product as a whole.

Citations
Cyber Resilience Act

Article 7(1) says integration of an Annex III product does not itself make the host product important.

European Commission CRA FAQs

Section 3.2 gives embedded-browser and secure-element examples and points back to the host product's core functionality.

Question 5

Can a product have extra functions and still be an important or critical product?

Yes. Additional or ancillary functions do not stop a product from being important or critical if the product's core functionality still matches a listed Annex III or Annex IV category.

The Commission FAQ gives examples: operating systems may include simple ancillary applications, and routers may integrate firewall functionality, without losing their operating-system or router core functionality. The reverse is also true: a product that can perform some SIEM-like functions is not automatically a SIEM if its actual core functionality is different.

Citations
Question 6

What is the conformity assessment consequence for a class I important product?

A class I important product can use the Article 32(1) procedures, including internal control based on module A, only when the Article 32(2) trigger is not met.

If the manufacturer has not applied, has applied only in part, or cannot use relevant harmonised standards, common specifications, or applicable European cybersecurity certification schemes at assurance level at least substantial for the relevant essential requirements, Article 32(2) requires either module B plus C or module H.

Citations
Cyber Resilience Act

Article 32(1) lists the baseline procedures; Article 32(2) sets the class I trigger for module B plus C or module H.

Question 7

What conformity assessment routes apply to class II important products?

Class II important products must use one of the Article 32(3) routes.

Those routes are module B plus C, module H, or, where available and applicable, a European cybersecurity certification scheme under Article 27(9) at assurance level at least substantial. Module A is not the ordinary route for class II, except for the separate free-and-open-source software rule in Article 32(5).

Citations
European Commission CRA FAQs

Section 6.2 states that module B plus C or H are mandatory for important products of class II, subject to the FOSS footnote.

Question 8

What conformity assessment routes apply to critical products?

Critical products follow Article 32(4). The first route is a European cybersecurity certification scheme in accordance with Article 8(1), if the Article 8(1) conditions are met.

If those conditions are not met, the critical product uses one of the Article 32(3) procedures: module B plus C, module H, or an available and applicable European cybersecurity certification scheme under Article 27(9) at assurance level at least substantial.

Citations
Cyber Resilience Act

Article 8(1) describes the certification route for critical products; Article 32(4) gives the fallback to Article 32(3) where Article 8(1) conditions are not met.

European Commission CRA FAQs

Section 6.2 describes critical products as using module B plus C or H unless future Article 8(1) certification becomes mandatory.

Question 9

Does important or critical status change the cybersecurity requirements themselves?

No. Important or critical status mainly changes the conformity assessment route before placing the product on the market.

The substantive CRA cybersecurity obligations still come from the essential cybersecurity requirements, the manufacturer's risk assessment, vulnerability handling obligations, technical documentation, and related manufacturer duties. Important and critical products do not get a separate Annex I; they get stricter assurance paths where the CRA requires them.

Citations
Cyber Resilience Act

Articles 6, 13, and 32 connect essential requirements, manufacturer risk assessment, and conformity assessment routes.

European Commission CRA FAQs

Section 3.3 explains that all products require a comprehensive cybersecurity risk assessment regardless of important or critical status.

Question 10

If only the core functionality drives classification, is only that core function assessed?

No. Core functionality determines the product class and route, but the conformity assessment still covers the product as a whole.

The draft Commission guidance explains that additional or ancillary functions can create additional cybersecurity risks. A manufacturer may be allowed to use internal control for a class I product where a harmonised standard covers the core functionality, but the manufacturer still has to address risks outside that standard's coverage.

Citations
Cyber Resilience Act

Article 32 requires conformity assessment of the product and the manufacturer's processes against the essential cybersecurity requirements.

Question 11

Can a higher-risk deployment environment move a product into a stricter important or critical class?

Not by itself. Classification turns on core functionality against Annex III or Annex IV, not only on whether a particular customer deploys the product in a sensitive environment.

Deployment risk still matters. The Commission FAQ gives a VPN example where one VPN version intended for critical infrastructure may require stronger risk treatment than another version intended for residential use. That affects the cybersecurity risk assessment and implementation of essential requirements, but it does not by itself rewrite the Annex III or Annex IV classification.

Citations
Cyber Resilience Act

Articles 7 and 8 use core functionality for classification; Article 13 ties implementation of essential requirements to risk.

Question 12

What is the free-and-open-source software rule for important products?

Article 32(5) gives a special route for products qualifying as free and open-source software that fall under Annex III.

If the product qualifies and the technical documentation is made public when the product is placed on the market, the manufacturer may use one of the Article 32(1) procedures. The text is limited to Annex III categories, so it does not create the same route for Annex IV critical products.

Citations
Cyber Resilience Act

Article 32(5) is limited to products qualifying as free and open-source software that fall under Annex III categories and make technical documentation public.

European Commission CRA FAQs

Sections 6.1 and 6.2 confirm that important class I or II FOSS can retain module A where Article 32(5) conditions are met.

Question 13

Can a manufacturer use product naming or documentation to avoid the stricter route?

No. The draft Commission guidance says the manufacturer may not misrepresent core functionality to escape the applicable conformity assessment regime.

Classification evidence should therefore align the product's instructions for use, promotional materials, sales statements, technical documentation, intended purpose, technical capabilities, and chosen conformity route. Inconsistencies between those records are a warning sign, especially for products close to Annex III or Annex IV categories.

Citations
Cyber Resilience Act

Annex VII requires technical documentation to include intended purpose and the conformity assessment procedure followed.

Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • The Commission FAQ identifies this act as the source of the technical descriptions for important and critical product categories.
"categories of important and critical products"
data.europa.eu
Referenced sections
  • Annex VII requires technical documentation to include intended purpose and the conformity assessment procedure followed.
"intended purpose"
ec.europa.eu
Referenced sections
  • Sections 6.1 and 6.2 confirm that important class I or II FOSS can retain module A where Article 32(5) conditions are met.
"free and open-source software"
Related guides

Explore more topics

CRA Applicability Test for Products With Digital Elements
Check whether the EU Cyber Resilience Act applies to a hardware, software, firmware, open-source, or connected product before conformity planning.
CRA Article 14 Reporting Obligations for Vulnerabilities and Incidents
Article 14 guide to CRA reports for actively exploited vulnerabilities and severe product-security incidents, including deadlines, CSIRT routing, users, and evidence.
CRA Blue Guide Concepts FAQ | Placing on the Market, Making Available, Distance Sales
CRA FAQ explaining Blue Guide market-access concepts for products with digital elements: placing on the market, making available, imports, CE marking, operator roles, online sales, stock, and testing exceptions.
CRA CE Marking FAQ | Conformity Assessment, EU Declaration, Evidence
Practical CRA CE marking answers for products with digital elements: conformity assessment, EU declaration, technical documentation, standards, software placement, and launch evidence.
CRA Component Due Diligence FAQ | Third-Party Software, FOSS, SBOMs
Cyber Resilience Act FAQ on manufacturer due diligence for integrated components, third-party software, FOSS dependencies, SBOMs, vulnerability handling, and evidence records.
CRA Conformity Assessment and CE Marking
How to choose a Cyber Resilience Act conformity route, prepare technical documentation, issue the EU declaration of conformity, and affix CE marking.
CRA Conformity Assessment Routes FAQ | Module A, Module B+C, Module H, Important and Critical Products
Cyber Resilience Act FAQ on when manufacturers can use module A, when module B+C or module H is required, and how important and critical products affect the route.
CRA Cybersecurity Risk Assessment FAQ | Article 13, Annex I, Updates
CRA FAQ on Article 13 cybersecurity risk assessments, Annex I applicability, intended purpose, foreseeable use, technical documentation, and update evidence.
CRA deadlines and compliance calendar | EU Cyber Resilience Act
Track the Cyber Resilience Act entry into force, staged application dates, Article 14 reporting deadlines, transitional rules, and review dates.
CRA Declaration of Conformity FAQ | Annex V, Simplified Declaration, CE Marking
FAQ on the Cyber Resilience Act EU Declaration of Conformity: Annex V contents, simplified Annex VI wording, CE marking link, technical documentation, retention, updates, and operator duties.
CRA Economic Operators FAQ | Manufacturers, Importers, Distributors, Authorised Representatives
CRA FAQ on economic-operator roles: manufacturers, importers, distributors, authorised representatives, substantial modification, traceability, and evidence controls.
CRA Essential Cybersecurity Requirements FAQ | Annex I Part I and Part II
CRA FAQ on Annex I product cybersecurity requirements, vulnerability handling, secure-by-default design, risk assessment, documentation, lifecycle duties, and user information.
CRA Essential Cybersecurity Requirements in Annex I
A grounded guide to the Cyber Resilience Act Annex I requirements for product security, vulnerability handling, secure-by-design controls, documentation, and evidence.
CRA Hardware and Software Boundaries FAQ | Product Scope, Components, RDPS
FAQ on Cyber Resilience Act hardware and software boundaries: combined products, standalone software, source code, components, remote data processing, SaaS and market-placement changes.
CRA Harmonised Standards FAQ | Presumption of Conformity, Common Specifications
Cyber Resilience Act FAQ on how harmonised standards, common specifications, certification schemes, and OJ publication affect CRA conformity evidence.
CRA Integrated Components and Dependencies FAQ | Third-Party Software and SBOM Evidence
Cyber Resilience Act FAQ on integrated components, third-party software, remote data processing, SBOM-style evidence, upstream fixes, FOSS dependencies, and manufacturer responsibility.
CRA Interplay With EU Product Laws FAQ | RED, Machinery, Data Act
Grounded CRA FAQ on overlap with the Radio Equipment Directive, Machinery Regulation, GPSR, Data Act, exclusions, declarations, documentation, and existing certificates.
CRA Known Exploitable Vulnerabilities at Launch FAQ
FAQ for Cyber Resilience Act launch decisions: known exploitable vulnerabilities, CVEs, component flaws, secure-by-default settings, release gates, Article 14 reporting, and evidence.
CRA Legacy Products FAQ | Pre-11 December 2027 Products
Cyber Resilience Act FAQ on products placed on the market before 11 December 2027, Article 14 reporting, substantial modification, distributor stock, spare parts, and records.
CRA Manufacturer Obligations FAQ | Article 13, Annex I, CE Marking
FAQ for Cyber Resilience Act manufacturers covering Article 13 duties, risk assessment, Annex I, vulnerability handling, support periods, documentation, conformity assessment, reporting, CE marking, and evidence controls.
CRA Market Surveillance and Enforcement FAQ | Authorities, Corrective Action, Safeguards
Cyber Resilience Act FAQ on market-surveillance authorities, investigations, corrective action, withdrawal, recall, safeguards, sweeps, documentation access, and penalties.
CRA Module B+C FAQ | EU-Type Examination, Conformity to Type, Notified Bodies
CRA Module B+C FAQ explaining EU-type examination, conformity to type, notified-body evidence, production control, CE marking, declarations, and certificate changes.
CRA Module H FAQ | Full Quality Assurance, Notified Body Surveillance, CE Marking
CRA Module H FAQ explaining the full-quality-assurance route, notified-body assessment, quality-system scope, technical documentation, CE marking, declarations, and records.
CRA Notified Bodies FAQ | Scope, Modules B+C and H, Certificates
Practical CRA FAQ on when notified bodies are needed, how CRA bodies are designated, what their notified scope means, and how Module B+C and Module H assessments work.
CRA Open-Source Software FAQ | FOSS Scope, Stewards, Manufacturers
Cyber Resilience Act FAQ for free and open-source software: commercial activity, steward duties, manufacturer due diligence, vulnerability handling, public documentation, and user obligations.
CRA Over-the-Air Updates FAQ
Cyber Resilience Act FAQ on OTA updates, automatic security updates, secure update distribution, support-period evidence, and offline update paths.
CRA penalties and fines FAQ | Article 64 fine caps
FAQ on EU Cyber Resilience Act Article 64 penalties: maximum fine tiers, turnover caps, national enforcement, economic operators, reporting duties, and open-source steward carve-outs.
CRA Penalties and Fines: Article 64 Caps and Enforcement Context
Article 64 of the EU Cyber Resilience Act sets administrative fine ceilings for Annex I, manufacturer, reporting, economic-operator, notified-body, and information-request breaches.
CRA Product Families FAQ | Variants, Shared Assessments, Family Reuse, Conformity Scope
CRA FAQ on product families, variant grouping, shared technical documentation, conformity evidence, and when cybersecurity-relevant differences need separate assessment.
CRA Products with Digital Elements Scope | EU Cyber Resilience Act
Apply the EU Cyber Resilience Act scope test for software, hardware, remote data processing, components, open-source software, exclusions, and economic-operator roles.
CRA Products With Digital Elements Scope FAQ
EU Cyber Resilience Act FAQ on products with digital elements, software, firmware, remote data processing, components, exclusions, market placement, and CRA operator boundaries.
CRA Remote Data Processing Solutions FAQ | Product Scope, Cloud and Backend Boundaries
FAQ on how the EU Cyber Resilience Act treats remote data processing solutions, manufacturer-controlled backends, third-party cloud services, SaaS, risk assessment, documentation, and user information.
CRA Reporting Obligations FAQ | Article 14, CSIRTs, ENISA, User Notices
Cyber Resilience Act FAQ on Article 14 reporting for actively exploited vulnerabilities and severe incidents, including timing, CSIRT routing, ENISA access, user notices, and evidence.
CRA Requirements | Annex I, Manufacturer Duties and CE Evidence
Map Cyber Resilience Act requirements from Annex I to manufacturer duties, vulnerability handling, user information, technical documentation, declaration of conformity, and CE marking evidence.
CRA SBOM and Vulnerability Management Template
Build a CRA-ready SBOM and vulnerability handling record with component inventory, triage, remediation, disclosure, reporting, update, and technical documentation fields.
CRA Secure-by-Default FAQ | Default Configuration and Annex I Controls
Cyber Resilience Act FAQ on secure-by-default configuration, automatic security updates, attack surface reduction, authentication, data minimisation, user information, and tailor-made products.
CRA Security Updates vs Functionality Updates FAQ
Cyber Resilience Act FAQ on classifying security updates, functionality updates, support-period duties, automatic updates, user notices, and substantial-modification review.
CRA Substantial Modification FAQ | Updates, Repairs, Manufacturer Duties
Cyber Resilience Act FAQ on when software updates, repairs, spare parts, and post-market changes become substantial modifications and trigger CRA manufacturer, evidence, and conformity duties.
CRA Support Period FAQ | Expected Product Lifetime, Security Updates, User Information
Practical CRA FAQ on how manufacturers determine support periods, disclose support end dates, keep security updates available, and document support-period evidence.
CRA Tailor-Made Products FAQ | Bespoke Products, Market Placement, Evidence
FAQ on when a bespoke product may be treated as tailor-made under the EU Cyber Resilience Act, what the carve-out changes, and what manufacturers still need to document.
CRA Technical Documentation FAQ | Annex VII Evidence and Technical File
CRA FAQ explaining Annex VII technical documentation, risk assessment evidence, conformity assessment files, vulnerability handling records, product families, RDPS, language, and authority access.
CRA Transition Period FAQ | Entry Into Force, Application Dates, Reporting, Legacy Products
CRA FAQ on the transition period covering entry into force, 2026 reporting, 2027 application, legacy products, stock, customs timing, and software versions.
CRA Update Availability and Software Archives FAQ
FAQ on CRA security-update availability, support-period notices, optional public software archives, historical versions, and Article 13(10) software-version limits.
CRA User Information and Transparency FAQ | Annex II Instructions
Practical CRA FAQ on Annex II user instructions, support-period disclosure, vulnerability contacts, update notices, importer and distributor information.
CRA vs RED Cybersecurity Delegated Act
Compare the EU Cyber Resilience Act with the RED cybersecurity delegated act for connected and radio equipment, including scope, timing, evidence, and transition treatment.
CRA vs UK PSTI Act | Cyber Resilience Act Comparison
Compare grounded EU Cyber Resilience Act duties with UK PSTI planning points, with UK legal details clearly marked for separate source review.
CRA Vulnerability Handling and Disclosure | Article 14 Reporting and Security Updates
How EU Cyber Resilience Act manufacturers should run vulnerability intake, remediation, coordinated disclosure, Article 14 reporting, secure updates, and evidence records.
CRA Vulnerability Handling FAQ | Support Periods, Components, Reporting
Practical CRA FAQ on vulnerability handling: SBOMs, remediation, coordinated disclosure, component issues, security updates, support periods, Article 14 reporting, and user notices.
Cyber Resilience Act Module A FAQ | Internal Production Control
FAQ on when CRA Module A internal production control is available, when it is blocked, and what documentation, testing, standards, and evidence it still requires.
EU CRA Compliance Program for Manufacturers and Economic Operators
Build a Cyber Resilience Act compliance program around product scope, Annex I security requirements, conformity assessment, technical documentation, vulnerability reporting, and market surveillance.
EU Cyber Resilience Act Checklist for Product Security and CE Marking
A CRA checklist for products with digital elements: scope, Annex I security controls, vulnerability handling, Article 14 reporting, technical documentation, conformity assessment, CE marking, and support-period evidence.
EU Cyber Resilience Act Core Functionality FAQ | CRA Product Classification
CRA FAQ on core functionality, product boundaries, remote data processing, integrated components, ancillary functions, and software changes that affect product classification.
EU Cyber Resilience Act FAQ
Direct CRA FAQ answers on scope, economic-operator roles, essential requirements, vulnerability reporting, conformity assessment, CE marking, support periods, and market surveillance.
EU Cyber Resilience Act Repairs and Spare Parts FAQ
CRA FAQ for repairs, spare parts, legacy products, security updates, substantial modification, and responsibility after product changes.
EU Cyber Resilience Act Technical Documentation and Audit File
Build an audit-ready CRA technical file around Article 31 and Annex VII: product scope, risk assessment, vulnerability handling, conformity evidence, testing, and retention.