FAQEUCyber Resilience Act

EU Cyber Resilience Act FAQ

Straight answers to the CRA questions that decide whether a product can be placed on the EU market and what evidence must exist before launch.

Use this page to orient product, engineering, security, compliance, legal, importer, distributor, and market-access reviews.

Author
Sorena AI
Published
Mar 10, 2026
Updated
Mar 10, 2026
FAQ modules
40

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 EU Cyber Resilience Act applies horizontal cybersecurity rules to products with digital elements. This FAQ summarizes the core market-access questions: what is in scope, who carries each role, what manufacturers must build and document, when vulnerability reports are triggered, how conformity assessment and CE marking work, how long support must last, and what market surveillance authorities can check.

Browse sub-FAQs

Choose the question set you need

These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.

Browse all FAQ items826
Focused FAQ modules
40
Showing 40 of 40
FAQ module

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.

33 items
FAQ module

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.

15 items
FAQ module

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.

14 items
FAQ module

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.

25 items
FAQ module

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.

5 items
FAQ module

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.

16 items
FAQ module

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.

27 items
FAQ module

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.

20 items
FAQ module

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.

14 items
FAQ module

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.

21 items
FAQ module

CRA Important and Critical Products FAQ | Annex III, Annex IV, Conformity Assessment

FAQ on CRA important and critical products, Annex III and Annex IV classification, core functionality, and conformity assessment consequences.

13 items
FAQ module

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.

22 items
FAQ module

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.

12 items
FAQ module

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.

14 items
FAQ module

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.

22 items
FAQ module

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.

17 items
FAQ module

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.

39 items
FAQ module

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.

32 items
FAQ module

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.

31 items
FAQ module

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.

23 items
FAQ module

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.

40 items
FAQ module

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.

26 items
FAQ module

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.

17 items
FAQ module

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.

16 items
FAQ module

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.

35 items
FAQ module

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.

16 items
FAQ module

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.

21 items
FAQ module

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.

17 items
FAQ module

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.

24 items
FAQ module

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.

20 items
FAQ module

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.

16 items
FAQ module

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.

13 items
FAQ module

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.

19 items
FAQ module

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.

23 items
FAQ module

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.

25 items
FAQ module

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.

17 items
FAQ module

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.

17 items
FAQ module

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.

16 items
FAQ module

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.

16 items
FAQ module

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.

17 items
Question 1

When is a product in scope of the EU Cyber Resilience Act?

A product is in CRA scope when it is a product with digital elements, is made available on the EU market, and its intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network.

Products with digital elements include software or hardware products and their remote data processing solutions, including software or hardware components placed on the market separately. The scope check still needs the Article 2 exclusions, such as certain products already covered by specified Union product regimes, and the national security or defence exclusion.

  • Check the product boundary: hardware, software, firmware, separately supplied components, and remote data processing that supports a product function.
  • Check the connection: direct or indirect logical or physical data connection, not just the presence of electronics.
  • Check market facts: each unit placed or made available on the EU market, including online and distance sales.
  • Check exclusions before assigning obligations, especially medical devices, in vitro diagnostic devices, certain vehicle and aviation products, marine equipment, and national security or defence use cases.
Question 2

Which CRA role does a company have: manufacturer, importer, distributor, or authorised representative?

The CRA assigns obligations by economic-operator role. A manufacturer develops, manufactures, or has a product designed, developed, or manufactured and markets it under its own name or trademark. Importers place products from outside the Union on the EU market, distributors make products available without affecting their properties, and authorised representatives act only within a written mandate from the manufacturer.

A company can have different roles for different products or channels. A business that sells a product under its own name or trademark can become the manufacturer even if another party designed or built the product. A third-country manufacturer also needs an EU-established operator able to perform the Article 4 tasks under the Market Surveillance Regulation.

  • Manufacturer evidence: product owner, brand or trademark, design and development responsibility, conformity assessment, technical documentation, EU declaration of conformity, CE marking, support period, and vulnerability handling.
  • Importer evidence: non-EU manufacturer link, EU establishment, checks that conformity assessment and documentation exist, CE marking and user information, and contact details.
  • Distributor evidence: supply-chain position, due-care checks before making available, handling that does not affect compliance, and escalation path for suspected non-compliance.
  • Authorised representative evidence: written mandate, tasks accepted, documentation availability, and limits showing that core manufacturer obligations have not been transferred.
Question 3

What are the CRA essential cybersecurity requirements?

The CRA splits essential cybersecurity requirements into product properties and vulnerability-handling processes. Manufacturers must design, develop, and produce products in line with Annex I Part I and must operate vulnerability handling in line with Annex I Part II throughout the support period.

The product-property requirements are applied through the manufacturer's cybersecurity risk assessment. If a Part I requirement is not applicable to the product, the manufacturer must justify that in the technical documentation. The vulnerability-handling requirements are not just launch checks; they continue during the support period.

  • Risk assessment: intended purpose, reasonably foreseeable use, conditions of use, operational environment, assets to protect, expected use time, and applicable essential requirements.
  • Product controls: secure-by-default configuration, protection against unauthorised access, data protection against compromise, attack-surface reduction, incident-impact limitation, and secure update mechanisms where applicable.
  • Vulnerability handling: identify and document components, address and remediate vulnerabilities, provide a vulnerability reporting contact point, maintain coordinated vulnerability disclosure policies, and make security updates available.
  • Documentation: include the cybersecurity risk assessment, support-period rationale, standards or specifications used, test reports, user information, and applicable SBOM information in the technical documentation.
Question 4

When must manufacturers report CRA vulnerabilities and severe incidents?

Manufacturers must notify actively exploited vulnerabilities contained in a product with digital elements and severe incidents having an impact on the security of that product. Notification is made via the single reporting platform to the CSIRT designated as coordinator and to ENISA.

An actively exploited vulnerability requires reliable evidence that a malicious actor exploited the vulnerability. A zero-day vulnerability is reportable when that condition is met, but a vulnerability found through good-faith testing without evidence of malicious exploitation is not automatically a mandatory Article 14 report.

  • Early warning: without undue delay and in any event within 24 hours after the manufacturer becomes aware.
  • Vulnerability notification: without undue delay and in any event within 72 hours after awareness, unless the relevant information was already provided.
  • User notice: after awareness, the manufacturer must inform impacted users, and where appropriate all users, about the vulnerability or incident and necessary mitigation or corrective measures.
  • Legacy products: Article 14 reporting applies to in-scope products placed on the market before 11 December 2027, once the reporting obligations apply.
Question 5

Which CRA conformity assessment route applies?

Conformity assessment is the legal procedure used to demonstrate that the product and the manufacturer's vulnerability-handling processes meet the CRA's essential requirements. The CRA routes are Module A internal control, Module B plus C EU-type examination with conformity to type, and Module H full quality assurance.

The default category can generally use Module A. Important and critical products may need a notified body, depending on the class, whether harmonised standards are applied, and whether another route such as a European cybersecurity certification scheme becomes mandatory for critical products.

  • Module A: the manufacturer verifies conformity and declares compliance on its own responsibility; no notified body participates.
  • Module B plus C: a notified body examines the technical design, development, and vulnerability-handling processes, while the manufacturer still controls production conformity.
  • Module H: the manufacturer operates a full quality system for design, development, production, final inspection, testing, and vulnerability handling, with notified-body assessment and surveillance.
  • Route evidence: product classification, harmonised-standard use, technical documentation, test evidence, notified-body certificate where required, and production controls.
Question 6

What does CRA CE marking mean for hardware and software products?

CE marking is the manufacturer's visible declaration that the product complies with applicable EU harmonisation legislation, including the CRA where it applies. It is not a mark of origin and does not mean a product was made in the EU.

Under the CRA, the manufacturer affixes the CE marking only after the relevant conformity assessment has a positive result, the EU declaration of conformity is drawn up, and the product satisfies the applicable requirements. Software products also need CE marking, either on the EU declaration of conformity or on the website accompanying the software product.

  • Physical products: affix CE marking visibly, legibly, and indelibly to the product, or where that is not possible, to packaging or accompanying documents.
  • Software products: affix the CE marking to the EU declaration of conformity or to an easily and directly accessible website section accompanying the software.
  • Notified-body number: include the notified body's identification number where the conformity assessment route requires it.
  • Formal non-compliance risk: missing or incorrect CE marking, declaration of conformity, notified-body number, or technical documentation can trigger corrective action.
Question 7

How long must the CRA support period last?

The manufacturer must determine the support period when placing the product on the market and must handle vulnerabilities effectively during that period. The period must reflect the expected use time, reasonable user expectations, product nature and intended purpose, relevant Union law, comparable products, operating environment availability, and support periods of core third-party components.

The CRA sets a support period of at least five years unless the product is expected to be in use for less than five years; in that case the support period must correspond to the expected use time. The end date, including at least the month and year, must be clearly available at purchase.

  • Minimum: at least five years unless the expected use time is shorter.
  • Longer products: if products are reasonably expected to be used for longer than five years, the support-period analysis may require longer support.
  • User transparency: disclose the support-period end date at purchase in an accessible way and, where applicable, on the product, packaging, or digitally.
  • Evidence: keep the support-period rationale in the technical documentation, including component support periods and expected-use assumptions.
Question 8

What can CRA market surveillance authorities do?

CRA market surveillance is handled under the EU market-surveillance framework for products with digital elements. Authorities can request information and documentation, evaluate compliance, require corrective action, and use restrictive measures such as withdrawal or recall where the CRA conditions are met.

Market surveillance can also address compliant products that still present a significant cybersecurity risk to health or safety, fundamental-rights compliance, services offered by essential entities, or other public-interest protections. Formal non-compliance is also enforceable, including missing CE marking, missing or incorrect EU declaration of conformity, missing notified-body identification number where applicable, or unavailable or incomplete technical documentation.

  • Documentation readiness: technical documentation, EU declaration of conformity, conformity-assessment evidence, support-period rationale, user instructions, and vulnerability-handling records.
  • Cooperation readiness: authority request intake, language handling, product identification, supply-chain traceability, and corrective-action owner.
  • Risk readiness: process for evaluating significant cybersecurity risks even when formal conformity evidence exists.
  • Formal compliance readiness: CE marking, notified-body number where applicable, complete declaration of conformity, and complete technical documentation.
Recommended next step

Turn CRA FAQ answers into product evidence

Use these CRA FAQ summaries to assign scope checks, role mapping, risk-assessment evidence, vulnerability-reporting intake, conformity-assessment records, CE marking controls, support-period rationale, and market-surveillance readiness tasks.

Primary sources

References and citations

ec.europa.eu
Referenced sections
  • Supports the general EU product-law meaning of CE marking as a manufacturer declaration, not a country-of-origin mark.
"not a mark of origin"
data.europa.eu
Referenced sections
  • Supports CRA market-surveillance powers, significant cybersecurity risk measures, formal non-compliance findings, withdrawal, and recall.
"market surveillance"
ec.europa.eu
Referenced sections
  • Explains that technical documentation must be available to market surveillance authorities and must demonstrate conformity.
"kept at the disposal of market surveillance authorities"
digital-strategy.ec.europa.eu
Referenced sections
  • Commission overview source for the CRA's purpose, product-security policy context, CE marking statement, national market-surveillance enforcement role, and application timing.
"Products will bear the CE marking"
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 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 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 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 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 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 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 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.
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 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.