--- title: "EU Cyber Resilience Act FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/cyber-resilience-act/faq" source_url: "https://www.sorena.io/artifacts/eu/cyber-resilience-act/faq/items/page/55" author: "Sorena AI" description: "Direct CRA FAQ answers on scope, economic-operator roles, essential requirements, vulnerability reporting, conformity assessment, CE marking, support periods, and market surveillance." published_at: "2026-03-10" updated_at: "2026-07-24" keywords: - "Cyber Resilience Act FAQ" - "CRA scope" - "CRA essential cybersecurity requirements" - "CRA vulnerability reporting" - "CRA CE marking" - "Cyber Resilience Act" - "CRA FAQ" - "products with digital elements" - "CE marking" - "vulnerability reporting" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # 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. *FAQ* *EU* *Cyber 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. This page helps orient product, engineering, security, compliance, legal, importer, distributor, and market-access reviews. The EU Cyber Resilience Act applies horizontal cybersecurity rules to products with digital elements made available on the Union market. Most obligations apply from 11 December 2027, while Article 14 reporting for actively exploited vulnerabilities and severe incidents starts on 11 September 2026. Use this overview to decide what is in scope, which economic operator carries each duty, what manufacturers must build and document, which conformity assessment route applies, how CE marking and support work, and what market surveillance authorities can check. Regulation (EU) 2024/2847 controls; the Commission-services FAQs cited here are non-binding interpretation. ## Definitions ### Products with digital elements Products with digital elements are software or hardware products and their remote data processing solutions, including software or hardware components placed on the market separately. CRA scope also requires Union-market availability and an intended or reasonably foreseeable direct or indirect logical or physical data connection, subject to the Article 2 exclusions. **Why it matters here:** This category sets the CRA product boundary. It can include standalone software, connected hardware, firmware, separately marketed components, and manufacturer-responsible remote processing needed for a product function. Sources: - [Regulation (EU) 2024/2847, Articles 2 and 3](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) ### Actively exploited vulnerability An actively exploited vulnerability is a vulnerability for which reliable evidence shows that a malicious actor exploited it in a system without the system owner's permission. A vulnerability found through good-faith testing is not actively exploited unless there is also reliable evidence of malicious exploitation. **Why it matters here:** This is one of the Article 14 reporting triggers from 11 September 2026. It is narrower than an exploitable vulnerability or a newly discovered zero-day vulnerability. Sources: - [Regulation (EU) 2024/2847, Articles 3(42) and 14](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) ### Support period The support period is the period during which the manufacturer must handle vulnerabilities effectively under CRA Annex I Part II. It must reflect the product's expected use and the factors in Article 13(8), and must last at least five years unless expected use is shorter. **Why it matters here:** The duration controls how long the manufacturer must operate vulnerability handling and affects security-update availability, user information, and record retention. The end date must be clear at purchase. Sources: - [Regulation (EU) 2024/2847, Articles 3(20) and 13(8)-(9), and Annex II](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) ## Browse sub-FAQ modules ### [CRA Blue Guide Concepts FAQ | Placing on the Market, Making Available, Distance Sales](/artifacts/eu/cyber-resilience-act/faq/blue-guide-concepts.md) 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. - 34 items ### [CRA CE Marking FAQ | Conformity Assessment, EU Declaration, Evidence](/artifacts/eu/cyber-resilience-act/faq/ce-marking.md) Practical CRA CE marking answers for products with digital elements: conformity assessment, EU declaration, technical documentation, standards, software placement, and launch evidence. - 15 items ### [CRA Component Due Diligence FAQ | Third-Party Software, FOSS, SBOMs](/artifacts/eu/cyber-resilience-act/faq/component-due-diligence.md) Cyber Resilience Act FAQ on manufacturer due diligence for integrated components, third-party software, FOSS dependencies, SBOMs, vulnerability handling, and evidence records. - 15 items ### [CRA Conformity Assessment Routes FAQ | Module A, Module B+C, Module H, Important and Critical Products](/artifacts/eu/cyber-resilience-act/faq/conformity-assessment-routes.md) 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 ### [CRA Cybersecurity Risk Assessment FAQ | Article 13, Annex I, Updates](/artifacts/eu/cyber-resilience-act/faq/cybersecurity-risk-assessment.md) CRA FAQ on Article 13 cybersecurity risk assessments, Annex I applicability, intended purpose, foreseeable use, technical documentation, and update evidence. - 10 items ### [CRA Declaration of Conformity FAQ | Annex V, Simplified Declaration, CE Marking](/artifacts/eu/cyber-resilience-act/faq/declaration-of-conformity.md) 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 ### [CRA Economic Operators FAQ | Manufacturers, Importers, Distributors, Authorised Representatives](/artifacts/eu/cyber-resilience-act/faq/economic-operators.md) CRA FAQ on economic-operator roles: manufacturers, importers, distributors, authorised representatives, substantial modification, traceability, and evidence controls. - 27 items ### [CRA Essential Cybersecurity Requirements FAQ | Annex I Part I and Part II](/artifacts/eu/cyber-resilience-act/faq/essential-cybersecurity-requirements.md) CRA FAQ on Annex I product cybersecurity requirements, vulnerability handling, secure-by-default design, risk assessment, documentation, lifecycle duties, and user information. - 20 items ### [CRA Hardware and Software Boundaries FAQ | Product Scope, Components, RDPS](/artifacts/eu/cyber-resilience-act/faq/hardware-software-boundaries.md) 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 ### [CRA Harmonised Standards FAQ | Presumption of Conformity, Common Specifications](/artifacts/eu/cyber-resilience-act/faq/harmonised-standards-and-common-specifications.md) Cyber Resilience Act FAQ on how harmonised standards, common specifications, certification schemes, and OJ publication affect CRA conformity evidence. - 22 items ### [CRA Important and Critical Products FAQ | Annex III, Annex IV, Conformity Assessment](/artifacts/eu/cyber-resilience-act/faq/important-and-critical-products.md) FAQ on CRA important and critical products, Annex III and Annex IV classification, core functionality, and conformity assessment consequences. - 14 items ### [CRA Integrated Components and Dependencies FAQ | Third-Party Software and SBOM Evidence](/artifacts/eu/cyber-resilience-act/faq/integrated-components-and-dependencies.md) Cyber Resilience Act FAQ on integrated components, third-party software, remote data processing, SBOM-style evidence, upstream fixes, FOSS dependencies, and manufacturer responsibility. - 23 items ### [CRA Interplay With EU Product Laws FAQ | RED, Machinery, Data Act](/artifacts/eu/cyber-resilience-act/faq/interplay-with-other-eu-laws.md) Official source CRA FAQ on overlap with the Radio Equipment Directive, Machinery Regulation, GPSR, Data Act, exclusions, declarations, documentation, and existing certificates. - 20 items ### [CRA Known Exploitable Vulnerabilities at Launch FAQ](/artifacts/eu/cyber-resilience-act/faq/known-exploitable-vulnerabilities-at-launch.md) 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 ### [CRA Legacy Products FAQ | Pre-11 December 2027 Products](/artifacts/eu/cyber-resilience-act/faq/legacy-products.md) 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 ### [CRA Manufacturer Obligations FAQ | Article 13, Annex I, CE Marking](/artifacts/eu/cyber-resilience-act/faq/manufacturer-obligations.md) 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 ### [CRA Market Surveillance and Enforcement FAQ | Authorities, Corrective Action, Safeguards](/artifacts/eu/cyber-resilience-act/faq/market-surveillance-and-enforcement.md) Cyber Resilience Act FAQ on market-surveillance authorities, investigations, corrective action, withdrawal, recall, safeguards, sweeps, documentation access, and penalties. - 39 items ### [CRA Module B+C FAQ | EU-Type Examination, Conformity to Type, Notified Bodies](/artifacts/eu/cyber-resilience-act/faq/module-b-c.md) 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 ### [CRA Module H FAQ | Full Quality Assurance, Notified Body Surveillance, CE Marking](/artifacts/eu/cyber-resilience-act/faq/module-h.md) 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 ### [CRA Notified Bodies FAQ | Scope, Modules B+C and H, Certificates](/artifacts/eu/cyber-resilience-act/faq/notified-bodies.md) 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 ### [CRA Open-Source Software FAQ | FOSS Scope, Stewards, Manufacturers](/artifacts/eu/cyber-resilience-act/faq/open-source-software.md) 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 ### [CRA Over-the-Air Updates FAQ](/artifacts/eu/cyber-resilience-act/faq/over-the-air-updates.md) Cyber Resilience Act FAQ on OTA updates, automatic security updates, secure update distribution, support-period evidence, and offline update paths. - 26 items ### [CRA penalties and fines FAQ | Article 64 fine caps](/artifacts/eu/cyber-resilience-act/faq/penalties-and-fines.md) 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. - 18 items ### [CRA Product Families FAQ | Variants, Shared Assessments, Family Reuse, Conformity Scope](/artifacts/eu/cyber-resilience-act/faq/product-families.md) CRA FAQ on product families, variant grouping, shared technical documentation, conformity evidence, and when cybersecurity-relevant differences need separate assessment. - 17 items ### [CRA Products With Digital Elements Scope FAQ](/artifacts/eu/cyber-resilience-act/faq/scope-and-products-with-digital-elements.md) 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 ### [CRA Remote Data Processing Solutions FAQ | Product Scope, Cloud and Backend Boundaries](/artifacts/eu/cyber-resilience-act/faq/remote-data-processing-solutions.md) 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 ### [CRA Reporting Obligations FAQ | Article 14, CSIRTs, ENISA, User Notices](/artifacts/eu/cyber-resilience-act/faq/reporting-obligations.md) 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 ### [CRA Secure-by-Default FAQ | Default Configuration and Annex I Controls](/artifacts/eu/cyber-resilience-act/faq/secure-by-default.md) Cyber Resilience Act FAQ on secure-by-default configuration, automatic security updates, attack surface reduction, authentication, data minimisation, user information, and tailor-made products. - 18 items ### [CRA Security Updates vs Functionality Updates FAQ](/artifacts/eu/cyber-resilience-act/faq/security-updates-vs-functionality-updates.md) Cyber Resilience Act FAQ on classifying security updates, functionality updates, support-period duties, automatic updates, user notices, and substantial-modification review. - 25 items ### [CRA Substantial Modification FAQ | Updates, Repairs, Manufacturer Duties](/artifacts/eu/cyber-resilience-act/faq/substantial-modification.md) 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. - 21 items ### [CRA Support Period FAQ | Expected Product Lifetime, Security Updates, User Information](/artifacts/eu/cyber-resilience-act/faq/support-period.md) Practical CRA FAQ on how manufacturers determine support periods, disclose support end dates, keep security updates available, and document support-period evidence. - 17 items ### [CRA Tailor-Made Products FAQ | Bespoke Products, Market Placement, Evidence](/artifacts/eu/cyber-resilience-act/faq/tailor-made-products.md) 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. - 14 items ### [CRA Technical Documentation FAQ | Annex VII Evidence and Technical File](/artifacts/eu/cyber-resilience-act/faq/technical-documentation.md) 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 ### [CRA Transition Period FAQ | Entry Into Force, Application Dates, Reporting, Legacy Products](/artifacts/eu/cyber-resilience-act/faq/transition-period.md) CRA FAQ on the transition period covering entry into force, 2026 reporting, 2027 application, legacy products, stock, customs timing, and software versions. - 24 items ### [CRA Update Availability and Software Archives FAQ](/artifacts/eu/cyber-resilience-act/faq/update-availability-and-archives.md) FAQ on CRA security-update availability, support-period notices, optional public software archives, historical versions, and Article 13(10) software-version limits. - 26 items ### [CRA User Information and Transparency FAQ | Annex II Instructions](/artifacts/eu/cyber-resilience-act/faq/user-information-and-transparency.md) Practical CRA FAQ on Annex II user instructions, support-period disclosure, vulnerability contacts, update notices, importer and distributor information. - 17 items ### [CRA Vulnerability Handling FAQ | Support Periods, Components, Reporting](/artifacts/eu/cyber-resilience-act/faq/vulnerability-handling.md) Practical CRA FAQ on vulnerability handling: SBOMs, remediation, coordinated disclosure, component issues, security updates, support periods, Article 14 reporting, and user notices. - 19 items ### [Cyber Resilience Act Module A FAQ | Internal Production Control](/artifacts/eu/cyber-resilience-act/faq/module-a.md) 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 ### [EU Cyber Resilience Act Core Functionality FAQ | CRA Product Classification](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md) CRA FAQ on core functionality, product boundaries, remote data processing, integrated components, ancillary functions, and software changes that affect product classification. - 16 items ### [EU Cyber Resilience Act Repairs and Spare Parts FAQ](/artifacts/eu/cyber-resilience-act/faq/repairs-and-spare-parts.md) CRA FAQ for repairs, spare parts, legacy products, security updates, substantial modification, and responsibility after product changes. - 18 items Browse all indexed questions: [/artifacts/eu/cyber-resilience-act/faq/items](/artifacts/eu/cyber-resilience-act/faq/items.md) ## All FAQ items *Page 55 of 58. Showing 15 of 856 items.* ### [Can important class II or critical products use Module A?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#can-important-class-ii-or-critical-products-use-module-a) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Important class II products cannot generally use Module A. Article 32(3) sends them to module B+C, module H, or a qualifying European cybersecurity certification scheme. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 32(3) and Article 32(4) set the routes for important class II and critical products. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ section 6.1 identifies class II and critical products as categories requiring stricter assessment routes, subject to the Article 32(5) exception. ### [What is the free and open-source software exception for Module A?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#what-is-the-free-and-open-source-software-exception-for-module-a) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Article 32(5) allows products qualifying as free and open-source software that fall within Annex III to use the Article 32(1) procedures, including Module A, if the Article 31 technical documentation is made available to the public when the product is placed on the market. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 32(5) creates the FOSS exception and requires public availability of the technical documentation for that route. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ section 6.6 confirms that public technical documentation is not generally required, except for the Article 32(5) FOSS self-attestation case. ### [What technical documentation is required under Module A?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#what-technical-documentation-is-required-under-module-a) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Module A still requires the manufacturer to draw up the technical documentation described in Annex VII. Article 31 requires that documentation to show how the product and the manufacturer's processes comply with Annex I. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 31 and Annex VII define the technical documentation content; Annex VIII Part I point 2 requires it for Module A. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ section 6.6 explains that technical documentation must be comprehensive and clear because market surveillance authorities may request it. ### [Does Module A require testing?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#does-module-a-require-testing) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Module A requires verification evidence, but the CRA does not mandate one single evaluation methodology. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Annex VII point 6 requires test reports for product and vulnerability-handling conformity where tests are carried out. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ section 6.5 covers evaluation methodology, internal and external laboratories, and manufacturer responsibility. ### [What production controls does Module A require?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#what-production-controls-does-module-a-require) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Module A is not limited to design review. Annex VIII Part I requires the manufacturer to take all measures necessary so that the design, development, production, vulnerability handling, and monitoring processes ensure compliance of both the product and the manufacturer's processes with Annex I. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Annex VIII Part I point 3 covers design, development, production, vulnerability handling, and monitoring under Module A. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ section 6.1 includes the manufacturer's duty to ensure that production of different units does not alter CRA compliance. ### [Do harmonised standards create Module A eligibility by themselves?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#do-harmonised-standards-create-module-a-eligibility-by-themselves) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* No. Harmonised standards, common specifications, and qualifying European cybersecurity certification schemes are conformity tools. They can provide presumption of conformity for covered requirements, but they are not the same thing as the conformity-assessment route. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 27 covers presumption of conformity tools; Article 32 separately governs conformity-assessment routes. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ sections 4.1.7 and 6.6 explain the role of harmonised standards and the need to document other technical means. ### [What should the standards coverage record show?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#what-should-the-standards-coverage-record-show) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* A standards coverage record should show which Annex I requirements are covered by each harmonised standard, common specification, or qualifying certification scheme; which parts were applied in full or in part; and which requirements were met by other technical solutions. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Annex VII point 5 requires a list of applied standards, specifications, or schemes and descriptions of other solutions where they are not applied. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ section 6.6 explains that the technical documentation must show how compliance with the essential requirements is demonstrated. ### [Can an authorised representative take over Module A?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#can-an-authorised-representative-take-over-module-a) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Only partly. An authorised representative may fulfil the CE-marking and EU declaration obligations in Annex VIII Part I point 4 on the manufacturer's behalf and under the manufacturer's responsibility if the mandate covers that work. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 18(2) limits the authorised representative mandate; Annex VIII Part I point 5 limits Module A representative tasks to point 4 obligations. ### [When can the CE marking and declaration be completed under Module A?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#when-can-the-ce-marking-and-declaration-be-completed-under-module-a) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* Only after the manufacturer has completed the applicable Module A conformity work with a positive result. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 28, Article 30, and Annex VIII Part I point 4 cover the CE marking and declaration steps after conformity assessment. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ sections 6.7 and 6.8 explain CE marking and declaration of conformity sequencing. ### [How long must Module A records be kept?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#how-long-must-module-a-records-be-kept) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* The manufacturer must keep the EU declaration of conformity together with the technical documentation at the disposal of national authorities for 10 years after the product has been placed on the market or for the support period, whichever is longer. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 31 and Annex VIII Part I point 4.2 cover continuous technical-documentation maintenance and record retention. ### [Does Module A stop market surveillance authorities from reviewing the product?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#does-module-a-stop-market-surveillance-authorities-from-reviewing-the-product) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* No. Module A removes notified-body involvement from the assessment route, but it does not remove market surveillance. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Articles 53, 54, and 58 cover access to documentation, national market-surveillance procedures, and formal non-compliance. ### [What evidence makes a Module A self-assessment defensible?](/artifacts/eu/cyber-resilience-act/faq/module-a.md#what-evidence-makes-a-module-a-self-assessment-defensible) *Module: [Cyber Resilience Act Module A](/artifacts/eu/cyber-resilience-act/faq/module-a.md)* A defensible Module A file should let a reviewer trace the compliance conclusion from product scope to requirement mapping to verification evidence. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 13, Article 31, Annex VII, and Annex VIII Part I together define the manufacturer obligations and evidence needed for Module A. - [European Commission CRA FAQs](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - FAQ sections 4.1.8, 6.1, 6.5, and 6.6 explain risk-assessment documentation, testing, technical documentation, and Module A responsibilities. ### [What is core functionality under the EU Cyber Resilience Act?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#what-is-core-functionality-under-the-eu-cyber-resilience-act) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* The CRA uses core functionality to classify products, but the regulation itself does not give a standalone definition. Non-binding draft Commission guidance published for feedback in March 2026 describes it as the product's main features and technical capabilities, without which the product could not meet its intended purpose. Sources for this answer: - [Draft Commission guidance on the CRA (March 2026 draft)](https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/16959-Draft-Commission-guidance-on-the-Cyber-Resilience-Act_en?ref=sorena.io) - Points 123 and 124 explain the draft guidance meaning of core functionality and the materials used to identify it. - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 3(23), Article 3(24), and Annex VII ground intended purpose, reasonably foreseeable use, and technical-documentation context. ### [Why does core functionality matter for CRA classification?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#why-does-core-functionality-matter-for-cra-classification) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* A product with digital elements is treated as important if it has the core functionality of a category in Annex III. Critical-product treatment is tied to the core functionality of categories in Annex IV, subject to the CRA mechanism for critical products. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Articles 7, 8, and 32 connect core functionality to important, critical, and default conformity-assessment routes. - [Draft Commission guidance on the CRA (March 2026 draft)](https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/16959-Draft-Commission-guidance-on-the-Cyber-Resilience-Act_en?ref=sorena.io) - Points 121 and 122 explain why core functionality determines the applicable conformity-assessment regime. ### [What source should manufacturers use to match a product to a listed CRA category?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#what-source-should-manufacturers-use-to-match-a-product-to-a-listed-cra-category) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Use the binding technical descriptions for important and critical product categories in Commission Implementing Regulation (EU) 2025/2392, not only Annex labels, draft-guidance examples, or market intuition. Sources for this answer: - [European Commission CRA FAQs (January 2026)](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - Section 3.1 identifies Implementing Regulation (EU) 2025/2392 as the source of the technical descriptions. - [Commission Implementing Regulation (EU) 2025/2392](https://eur-lex.europa.eu/eli/reg_impl/2025/2392/oj/eng?ref=sorena.io) - The implementing regulation provides the technical descriptions used for important and critical category matching. - [Draft Commission guidance on the CRA (March 2026 draft)](https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/16959-Draft-Commission-guidance-on-the-Cyber-Resilience-Act_en?ref=sorena.io) - Footnote 15 and examples 48 to 53 apply those technical descriptions in core-functionality analysis. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/cyber-resilience-act/faq/items](/artifacts/eu/cyber-resilience-act/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 55 of 58 Pages: [1](/artifacts/eu/cyber-resilience-act/faq/items.md) | [2](/artifacts/eu/cyber-resilience-act/faq/items/page/2.md) | [3](/artifacts/eu/cyber-resilience-act/faq/items/page/3.md) | [4](/artifacts/eu/cyber-resilience-act/faq/items/page/4.md) | [5](/artifacts/eu/cyber-resilience-act/faq/items/page/5.md) | [6](/artifacts/eu/cyber-resilience-act/faq/items/page/6.md) | [7](/artifacts/eu/cyber-resilience-act/faq/items/page/7.md) | [8](/artifacts/eu/cyber-resilience-act/faq/items/page/8.md) | [9](/artifacts/eu/cyber-resilience-act/faq/items/page/9.md) | [10](/artifacts/eu/cyber-resilience-act/faq/items/page/10.md) | [11](/artifacts/eu/cyber-resilience-act/faq/items/page/11.md) | [12](/artifacts/eu/cyber-resilience-act/faq/items/page/12.md) | [13](/artifacts/eu/cyber-resilience-act/faq/items/page/13.md) | [14](/artifacts/eu/cyber-resilience-act/faq/items/page/14.md) | [15](/artifacts/eu/cyber-resilience-act/faq/items/page/15.md) | [16](/artifacts/eu/cyber-resilience-act/faq/items/page/16.md) | [17](/artifacts/eu/cyber-resilience-act/faq/items/page/17.md) | [18](/artifacts/eu/cyber-resilience-act/faq/items/page/18.md) | [19](/artifacts/eu/cyber-resilience-act/faq/items/page/19.md) | [20](/artifacts/eu/cyber-resilience-act/faq/items/page/20.md) | [21](/artifacts/eu/cyber-resilience-act/faq/items/page/21.md) | [22](/artifacts/eu/cyber-resilience-act/faq/items/page/22.md) | [23](/artifacts/eu/cyber-resilience-act/faq/items/page/23.md) | [24](/artifacts/eu/cyber-resilience-act/faq/items/page/24.md) | [25](/artifacts/eu/cyber-resilience-act/faq/items/page/25.md) | [26](/artifacts/eu/cyber-resilience-act/faq/items/page/26.md) | [27](/artifacts/eu/cyber-resilience-act/faq/items/page/27.md) | [28](/artifacts/eu/cyber-resilience-act/faq/items/page/28.md) | [29](/artifacts/eu/cyber-resilience-act/faq/items/page/29.md) | [30](/artifacts/eu/cyber-resilience-act/faq/items/page/30.md) | [31](/artifacts/eu/cyber-resilience-act/faq/items/page/31.md) | [32](/artifacts/eu/cyber-resilience-act/faq/items/page/32.md) | [33](/artifacts/eu/cyber-resilience-act/faq/items/page/33.md) | [34](/artifacts/eu/cyber-resilience-act/faq/items/page/34.md) | [35](/artifacts/eu/cyber-resilience-act/faq/items/page/35.md) | [36](/artifacts/eu/cyber-resilience-act/faq/items/page/36.md) | [37](/artifacts/eu/cyber-resilience-act/faq/items/page/37.md) | [38](/artifacts/eu/cyber-resilience-act/faq/items/page/38.md) | [39](/artifacts/eu/cyber-resilience-act/faq/items/page/39.md) | [40](/artifacts/eu/cyber-resilience-act/faq/items/page/40.md) | [41](/artifacts/eu/cyber-resilience-act/faq/items/page/41.md) | [42](/artifacts/eu/cyber-resilience-act/faq/items/page/42.md) | [43](/artifacts/eu/cyber-resilience-act/faq/items/page/43.md) | [44](/artifacts/eu/cyber-resilience-act/faq/items/page/44.md) | [45](/artifacts/eu/cyber-resilience-act/faq/items/page/45.md) | [46](/artifacts/eu/cyber-resilience-act/faq/items/page/46.md) | [47](/artifacts/eu/cyber-resilience-act/faq/items/page/47.md) | [48](/artifacts/eu/cyber-resilience-act/faq/items/page/48.md) | [49](/artifacts/eu/cyber-resilience-act/faq/items/page/49.md) | [50](/artifacts/eu/cyber-resilience-act/faq/items/page/50.md) | [51](/artifacts/eu/cyber-resilience-act/faq/items/page/51.md) | [52](/artifacts/eu/cyber-resilience-act/faq/items/page/52.md) | [53](/artifacts/eu/cyber-resilience-act/faq/items/page/53.md) | [54](/artifacts/eu/cyber-resilience-act/faq/items/page/54.md) | [55](/artifacts/eu/cyber-resilience-act/faq/items/page/55.md) | [56](/artifacts/eu/cyber-resilience-act/faq/items/page/56.md) | [57](/artifacts/eu/cyber-resilience-act/faq/items/page/57.md) | [58](/artifacts/eu/cyber-resilience-act/faq/items/page/58.md) [Previous page](/artifacts/eu/cyber-resilience-act/faq/items/page/54.md) | [Next page](/artifacts/eu/cyber-resilience-act/faq/items/page/56.md) *Recommended next step* *Placement: after the FAQ summaries* ## 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. - [Open Assessment Autopilot](/solutions/assessment.md): Convert CRA scope, role, support-period, and conformity questions into evidence requests and review tasks. - [Talk through CRA readiness](/contact.md): Review product boundaries, launch blockers, vulnerability-handling evidence, and market-access records with the Sorena team. --- [Privacy Policy](https://www.sorena.io/privacy.md) | [Terms of Use](https://www.sorena.io/terms-of-use.md) | [DMCA](https://www.sorena.io/dmca.md) | [About Us](https://www.sorena.io/about-us.md) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/cyber-resilience-act/faq/items/page/55.md