FAQEUCyber Resilience Act

EU Cyber Resilience Act FAQ Conformity Assessment Routes

This CRA FAQ helps understand which route applies, when is enough, when or is required, and how standards, certification schemes, and product classification affect the answer.

Built for compliance, certification, product, legal, and engineering teams planning CRA market access.

Author
Sorena AI
Published
Mar 10, 2026
Updated
Oct 15, 2026
Overview

Choose the CRA route only after fixing the product boundary and classification. Default-category products may use . Important class I products may use module A only under the Article 32(2) conditions. Important class II products generally require , , or a qualifying certification route, while critical products can be subject to further Commission requirements. These route duties generally apply to products placed on the Union market from 11 December 2027, subject to the CRA's transitional rules. This FAQ explains those branches and what evidence each route still requires. The Regulation controls; Commission-services FAQs and adopted Commission guidance cited here are non-binding interpretation.

Search this module

Find a question or answer quickly

25 of 25 questions
Question 1

What conformity assessment routes does the CRA recognise?

The CRA recognises the four conformity routes listed below.

A cybersecurity certificate is not automatically a CRA conformity route. The relevant certification scheme must be specified for CRA purposes under Article 27(9), cover the applicable requirements or assurance conditions, and be available for the product category.

  • internal control based on
  • EU-type examination based on module B followed by conformity to EU-type based on module C
  • full quality assurance based on
  • where available and applicable, a European cybersecurity certification scheme specified under Article 27(9)
Recommended next step

Check the evidence behind a CRA conformity route

Use Research Copilot to compare a product's CRA classification, standards coverage, certification evidence, and notified-body needs before release planning.

Question 2

What decides which CRA conformity assessment route a manufacturer has to use?

The starting point is the product's classification under the CRA.

Manufacturers first need to determine whether the product is in the default category, an important product of class I, an important product of class II, or a critical product. That depends on the product's core functionality, not simply on the fact that it includes components that are themselves important or critical products.

Question 3

Which CRA conformity assessment route applies to products in the default category?

Products in the default category can always use .

They may also use or if the manufacturer chooses, because Article 32(1) makes those routes generally available. The key point is that the CRA does not require third-party for default-category products.

Question 4

When can an important CRA class I product use module A?

An important product of class I can use if, in assessing compliance, the manufacturer has applied relevant harmonised standards, common specifications, or European cybersecurity certification schemes at assurance level at least substantial.

If those instruments have not been applied, have been applied only in part, or do not exist, Article 32(2) requires the relevant essential cybersecurity requirements to be covered through or instead. The non-binding July 2026 Commission guidance explains that a class I manufacturer may use internal control when all applicable requirements of a relevant standard whose reference is published in the Official Journal are applied and its scope covers at least all core-functionality risks. Additional risks outside that scope need other documented measures, as the following answer explains.

Question 5

What if a harmonised standard covers the core functionality of an important class I product, but not every cybersecurity risk of the full product?

The Commission guidance adopted in July 2026 takes the view that the manufacturer may still use internal control if the harmonised standard covers the product's core functionality.

But that does not mean the whole product automatically benefits from a full presumption of conformity. The guidance explains that the manufacturer still has to address additional risks presented by broader product scope or additional functions, and the presumption of conformity extends only to the parts covered by the standard.

Question 6

Which CRA conformity assessment routes apply to important products of class II?

Important products of class II must use one of the routes listed below.

Outside the free and open-source software exception in Article 32(5), is not available for class II products.

  • where available and applicable, a European cybersecurity certification scheme specified under Article 27(9) at assurance level at least substantial
Question 7

Which CRA conformity assessment routes apply to critical products with digital elements?

Critical products listed in Annex IV follow one of the routes listed below.

So critical products do not automatically have to use the same third-party route in every case. The legal answer depends first on whether a certification scheme has been made mandatory under Article 8(1).

  • a European cybersecurity certification scheme where Article 8(1) requires one, or
  • if the conditions in Article 8(1) are not met, one of the class II routes in Article 32(3)
Question 8

Does integrating an important or critical component automatically force the finished product into the corresponding route?

No.

The CRA and the Commission FAQ both say that integrating an important or critical product into another product does not by itself make the finished product subject to the regime for that component category. The decisive factor is the core functionality of the finished product as a whole.

Question 9

Does the CRA provide a special route for free and open-source software in Annex III categories?

Yes.

Manufacturers of products qualifying as free and open-source software that fall under Annex III categories may use any of the Article 32(1) procedures, including , provided that the technical documentation is made available to the public at the time of placing the product on the market.

Question 10

Can a manufacturer choose a stricter CRA conformity assessment route than the minimum route required by law?

Yes.

The CRA sets minimum route requirements for certain product categories, but the manufacturer can still choose a more demanding route. For example, a default-category product may still go through or , and a class I product that could rely on may still opt for third-party assessment.

Question 11

What does CRA module A mean in practice?

is the internal control route.

Under this route, the manufacturer verifies that the product complies with the CRA, draws up the technical documentation, performs the necessary testing or equivalent verification, and declares compliance on its sole responsibility. No participates.

Question 12

What does CRA module B+C mean in practice?

combines notified-body examination of the design and development phase with manufacturer responsibility for conformity to the approved type in production.

The examines the design, technical documentation, supporting evidence and specimens under module B. The manufacturer then ensures under module C that the manufactured units conform to the approved type and remains responsible for production conformity.

Question 13

What does CRA module H mean in practice?

is full quality assurance.

Under this route, the manufacturer operates an approved quality system covering design, development, production, final inspection and testing, and a assesses and surveils that system. This is why can be attractive for manufacturers with larger product portfolios or products subject to frequent updates.

Question 14

Do CRA conformity assessment routes assess only the product, or also the manufacturer's processes?

They assess both.

Article 32 requires of the product with digital elements and the processes put in place by the manufacturer. That is why the Annex VIII procedures also cover vulnerability handling processes and, depending on the route, production controls or quality-system controls.

Question 15

How do high-risk AI systems affect CRA route selection?

As a rule, Article 12 says the relevant procedure under the AI Act applies to products that are both CRA products and high-risk AI systems, for the cybersecurity requirements addressed by the CRA.

But the CRA creates an important derogation. Important and critical CRA products that are also high-risk AI systems, and that would otherwise only be subject to AI Act internal control, must still follow the CRA procedures for the CRA cybersecurity requirements.

Question 16

Can existing certificates issued under other EU product laws still be used during the CRA transition?

Yes, but only within limits.

Article 69(1) says EU-type examination certificates and approval decisions issued regarding cybersecurity requirements under other Union harmonisation legislation remain valid until 11 June 2028 unless they expire earlier or the other legislation says otherwise. The Commission guidance adopted in July 2026 adds that manufacturers may rely on those certificates only for the cybersecurity risks and corresponding requirements they actually cover, and that even if the other legislation gives a longer validity period, reliance for CRA purposes does not continue beyond 11 June 2028.

Question 17

Do products designed before 11 December 2027 still need a CRA conformity assessment if new units are placed on the market later?

Yes.

The CRA applies to individual products placed on the market from 11 December 2027 onward, not only to newly designed product types. The Commission guidance adopted in July 2026 explains, however, that for products designed before the CRA applied, the manufacturer can demonstrate compliance through a current cybersecurity risk assessment and technical documentation and is not automatically expected to recreate historical design-phase evidence that would not improve the product's security.

Question 18

Can an important product of class I rely on a harmonised standard before its reference is published in the Official Journal?

No.

For CRA presumption of conformity and for the Article 32(2) route logic, a harmonised standard counts only once its reference has been published in the Official Journal of the European Union. The Commission FAQ also says that after the European standardisation organisations adopt a harmonised standard, the Commission still has to assess it before publication in the Official Journal. Until then, a manufacturer may still refer to it in its technical documentation as part of the technical solution it relies on, but it does not have the legal effect of a published harmonised standard under Article 27.

Question 19

Do common specifications and European cybersecurity certification schemes play the same role as harmonised standards for important class I route selection?

Broadly yes, where the CRA makes them available for that purpose.

Article 32(2) does not rely only on harmonised standards. It also refers to common specifications and European cybersecurity certification schemes at assurance level at least substantial as referred to in Article 27. The Commission guidance adopted in July 2026 says that, although it discusses harmonised standards for brevity, the same logic extends to common specifications and to European cybersecurity certification schemes specified by the Commission under Article 27(9). That means they can support the internal control route for important class I products only to the extent that they cover the relevant requirements. For certification schemes, the CRA also says that a European cybersecurity certificate at assurance level at least substantial removes the need for third-party CRA assessment only for the corresponding requirements, not automatically for everything else.

Question 20

For important or critical products, does the conformity assessment look only at the listed core functionality?

No.

The core functionality determines which route applies, but the conformity assessment itself covers the product as a whole. The adopted Commission guidance says the manufacturer needs to ensure that the whole product undergoes the applicable conformity assessment procedure, taking into account integrated components or additional functions as appropriate. The Commission FAQ says the in examines the whole product and all relevant essential requirements.

Question 21

Is CRA module B just a documentation review?

No.

Under Annex VIII, module B includes examination of the technical documentation and supporting evidence, but also examination of specimens of one or more critical parts of the product. The must carry out appropriate examinations and tests, or have them carried out. The Commission FAQ also states that the notified body does not only perform a documentation-based assessment and may perform the necessary tests itself or through an external laboratory. Separately, the manufacturer may use its own laboratory or another laboratory on its behalf and under its responsibility for supporting evidence.

Question 22

What happens to a CRA module B+C certificate if the product changes after certification?

Changes that may affect conformity or the certificate's validity need notified-body involvement.

Annex VIII requires the manufacturer to inform the of modifications to the approved type or vulnerability handling processes that may affect conformity with Annex I or the conditions for validity of the EU-type examination certificate. Those changes require additional approval as an addition to the original certificate. The Commission FAQ adds that substantial modifications require a new assessment by the same or a different notified body, while changes that do not affect CRA compliance are not subject to reassessment. Separately, Annex VIII Part II includes notified-body periodic audits focused on vulnerability-handling processes, while Module C leaves production conformity control with the manufacturer.

Question 23

Can CRA module H cover more than one product or product category, and does that remove future notified-body involvement?

It can cover products or product categories, but it does not eliminate ongoing notified-body control.

Annex VIII says can apply to the products with digital elements or product categories concerned, and the application must include technical documentation for one model of each intended category. But the manufacturer still has to keep the informed of intended changes to the quality system, and the notified body must decide whether the modified system remains acceptable or needs reassessment. The Commission FAQ also says the quality system can be extended to new or substantially modified products, but that extension remains subject to a new assessment by the same notified body.

Question 24

Are there CRA measures to reduce the conformity assessment burden for microenterprises and SMEs?

Yes.

The CRA says fees for procedures must take account of the specific interests and needs of microenterprises and SMEs and be reduced proportionately. It also requires notified bodies to carry out conformity assessments proportionately and without unnecessary burden. Beyond fees, Member States are to support awareness, advice, testing and conformity assessment activities where appropriate, may establish cyber resilience regulatory sandboxes, and microenterprises and small enterprises may use a simplified technical documentation format once specified by the Commission.

Question 25

If the Commission later reclassifies a product or mandates certification for a critical category, does the new CRA conformity assessment route apply immediately?

Not necessarily.

If the Commission amends Annex III to add, move or withdraw an important-product category, the delegated act must, where appropriate, provide a minimum transitional period of 12 months before the new Article 32(2) or 32(3) routes apply, unless urgency justifies a shorter period. If the Commission makes European cybersecurity certification mandatory for a critical category under Article 8(1), the delegated act must provide a minimum transitional period of six months, unless imperative urgency justifies a shorter one.

Primary sources

References and citations

data.europa.eu26 citations
Referenced sections
  • Official Cyber Resilience Act legal text supporting this FAQ and its article-level compliance conclusions.
  • Article 32(1) lists the available CRA conformity assessment procedures; Annex VIII defines modules A, B, C, and H.
  • Article 7(1), Article 8(1), and Article 32 connect product classification to the applicable conformity assessment route.
Show 23 more
  • Article 32(1) makes module A, module B+C, module H, and qualifying certification schemes available for products not pushed into stricter routes.
  • Article 27 and Article 32(2) explain when standards, common specifications, or certification schemes keep class I products on module A.
  • Article 27, Article 32(2), and Annex VII point 5 support the distinction between route eligibility and actual presumption of conformity.
  • Article 32(3) lists the class II routes; Article 32(5) creates the specific FOSS exception.
  • Article 8(1) and Article 32(4) set the certification-first rule for critical products and the fallback to class II routes.
  • Article 7(1) says integrating an Annex III product does not by itself move the larger product into the Annex III route.
  • Article 32(5) permits Annex III FOSS products to use Article 32(1) routes if public technical documentation is available.
  • Article 32(1) allows manufacturers to choose among the listed procedures when no stricter Article 32 route applies.
  • Annex VIII Part I defines module A as internal control on the manufacturer's sole responsibility.
  • Annex VIII Parts II and III define EU-type examination by a notified body followed by internal production control.
  • Annex VIII Part IV defines module H as full quality assurance covering design, development, production, final inspection, and testing.
  • Article 32(1) and Annex VIII require assessment of both the product and the manufacturer's relevant processes.
  • Article 12(2) and Article 12(3) explain when AI Act conformity assessment applies and when CRA procedures still govern CRA cybersecurity requirements.
  • Article 69(1) preserves certain existing cybersecurity certificates and approval decisions during the CRA transition, subject to limits.
  • Article 13(12) and Article 69(2) tie conformity assessment and technical documentation to products placed on the market after the CRA application point.
  • Article 27, Article 32(2), and Annex VII point 5 support the need for OJ-published references before standards affect CRA presumption and route evidence.
  • Article 27 and Article 32(2) explain how common specifications and qualifying cybersecurity certificates can affect third-party assessment obligations.
  • Article 32(1) to Article 32(4) link product classification to the route while still assessing the product and manufacturer processes.
  • Annex VIII Part II points 2, 3.4, and 4.1 to 4.5 require technical-documentation review, specimen examination, and appropriate tests.
  • Annex VIII Part II points 6 to 8 require notified-body approval for changes that may affect conformity or certificate validity.
  • Annex VIII Part IV points 1, 3.1, 3.5, and 4.3 explain product-category coverage and ongoing notified-body control under module H.
  • Article 32(6), Article 33, Article 39(12), Article 47(2), and Article 33(5) support proportionate assessment, SME fee reductions, support measures, sandboxes, and simplified documentation.
  • Article 7(3) and Article 8(1) set transitional-period rules for later Annex III changes and mandatory certification for critical categories.
ec.europa.eu19 citations
Referenced sections
  • Section 6 summarises the CRA conformity assessment routes and their relative complexity and external involvement.
  • Sections 3.1, 3.2, and 6 explain that core functionality, not merely integrated components, drives route selection.
  • Sections 6.1 and 6.2 distinguish self-assessment under module A from notified-body involvement under module B+C.
Show 16 more
  • Sections 6.1 and 6.2 explain when important class I products may use module A and when module B+C is required.
  • Sections 6.1 and 6.2 explain that class II products generally require module B+C, module H, or qualifying certification.
  • Section 6.2 explains notified-body involvement under module B+C where critical products fall back to Article 32(3).
  • Sections 3.2 and 3.4 give examples showing that integrated components and ancillary functions do not override core functionality.
  • Sections 6.1 and 6.2 describe the FOSS exception alongside module A and module B+C eligibility.
  • Sections 6.1, 6.2, and 6.3 describe module A, module B+C, and module H as increasingly involved options.
  • Section 6.1 explains the practical module A activities: mitigation, verification, technical documentation, CE marking, and production control.
  • Section 6.2 explains that module B+C involves one notified body for the design assessment while production conformity remains with the manufacturer.
  • Section 6.3 explains module H as a notified-body assessment and surveillance of the manufacturer's quality system.
  • Sections 6.1, 6.2, and 6.3 explain how product testing, vulnerability handling, production control, and quality-system controls appear across routes.
  • Section 6.4 explains that legacy product types are not exempt when new units are placed on the market after CRA applicability.
  • Section 6.10 explains the Commission assessment and Official Journal publication step for CRA harmonised standards.
  • Section 6.2 states that module B+C examines the whole product and all relevant essential requirements.
  • Sections 6.2 and 6.5 explain notified-body testing under module B and the manufacturer's supporting testing options.
  • Section 6.2 explains reassessment for substantial modifications and periodic audits of vulnerability-handling processes.
  • Section 6.3 explains that extending a module H quality system to new or substantially modified products still needs notified-body assessment.
ec.europa.eu9 citations
Referenced sections
  • Commission guidance, section 6, points 136–144. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 6, point 137. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 6.2–6.3, points 149–155. Supports the interpretation and qualifications explained in this answer.
Show 6 more
  • Commission guidance, section 6.2, point 148. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 6.1–6.2, points 141 and 152. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 9.3.2, points 247–254. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 2.7, points 33–39. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 6.2, points 148–152 and footnote 25. Supports the interpretation and qualifications explained in this answer.
  • Commission guidance, section 6.2, points 147 and 152. Supports the interpretation and qualifications explained in this answer.

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 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 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.

Show all related guides (55)

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 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 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.

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

Official source 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 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 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 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 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 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 Repairs and Spare Parts FAQ

CRA FAQ for repairs, spare parts, legacy products, security updates, substantial modification, and responsibility after product changes.

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 source-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 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 CRA vs UK PSTI Product Security Regime

Compare EU Cyber Resilience Act and UK PSTI product-security scope, duties, evidence, dates, actors, and enforcement for connected products.

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 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 Technical Documentation and Audit File

Build a CRA technical file around Article 31 and Annex VII: product scope, risk assessment, vulnerability handling, conformity evidence, testing, updates, and retention.