--- 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/56" 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 56 of 58. Showing 15 of 856 items.* ### [Is CRA core functionality assessed for the whole product or for one embedded component?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#is-cra-core-functionality-assessed-for-the-whole-product-or-for-one-embedded-component) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Assess the product as a whole. Integrating a component that itself performs an important or critical function does not automatically give the finished product that component's classification. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 7(1) says integration of an Annex III product does not by itself trigger the corresponding important-product conformity procedures. - [European Commission CRA FAQs (January 2026)](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - Section 3.2 gives browser/news-app and secure-element/laptop examples. - [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) - Point 126 and Example 49 explain that the finished product's core functionality controls. ### [How should teams draw the product boundary before deciding core functionality?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#how-should-teams-draw-the-product-boundary-before-deciding-core-functionality) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Start with whether there is a product with digital elements: a software or hardware product and its remote data processing solutions, including software or hardware components placed on the market separately. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 3(1) defines products with digital elements and includes remote data processing solutions and separately placed components. - [European Commission CRA FAQs (January 2026)](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - Section 1.1 gives examples of hardware, standalone software, software supplied with hardware, and remote data processing solutions. - [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) - The scope guidance explains that hardware and software can form one product where they operate together to perform intended functions. ### [Can a product perform many functions but still have one core functionality for CRA classification?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#can-a-product-perform-many-functions-but-still-have-one-core-functionality-for-cra-classification) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Yes. The draft guidance says a product may not have more than one core functionality for deciding the applicable conformity-assessment regime. Sources for this answer: - [European Commission CRA FAQs (January 2026)](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - Section 3.4 explains that additional functions do not by themselves negate a listed core functionality. - [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 125 and 128 explain ancillary functionality and the one-core-functionality approach for conformity-assessment classification. ### [Do ancillary functions ever change the CRA conformity-assessment work?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#do-ancillary-functions-ever-change-the-cra-conformity-assessment-work) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Ancillary functions may not change the category, but they still matter for the whole-product risk assessment and conformity evidence. The manufacturer must assess the product as a whole and address risks from additional functions or integrated components. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 13(2) and Annex VII require a cybersecurity risk assessment and technical documentation for the product. - [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 131, 134, 135, and Example 52 explain whole-product assessment where additional functions create risks. ### [Can a product fall outside a listed category even if it overlaps with that category?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#can-a-product-fall-outside-a-listed-category-even-if-it-overlaps-with-that-category) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Yes. Partial overlap is not enough. The draft guidance says similar domain, purpose, or deployment context does not prove shared core functionality. Sources for this answer: - [European Commission CRA FAQs (January 2026)](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - Section 3.4 explains that SOAR software is generally not treated as having SIEM core functionality. - [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) - Point 127 and Examples 50 and 51 distinguish products that exceed or fall short of a listed category. ### [Does use in a critical environment make a product important or critical under the CRA?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#does-use-in-a-critical-environment-make-a-product-important-or-critical-under-the-cra) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* No. Deployment environment alone does not supersede the core-functionality test. A product used in a sensitive or critical setting still needs to match the core functionality of an important or critical category before that category applies. Sources for this answer: - [European Commission CRA FAQs (January 2026)](https://ec.europa.eu/newsroom/dae/redirection/document/122331?ref=sorena.io) - Section 3.3 explains the VPN example and the distinction between classification and product-specific risk assessment. - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 13(2) and Article 13(3) require risk assessment based on intended purpose, reasonably foreseeable use, and conditions of use. ### [How do remote data processing solutions affect core functionality and product boundaries?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#how-do-remote-data-processing-solutions-affect-core-functionality-and-product-boundaries) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Remote data processing can be part of the product with digital elements, but it is not limited to the product's core functionality. The draft guidance says the remote-processing test covers functions that directly fulfil the product's intended purpose and functions that support the product's overall performance. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 3(1) and Article 3(2) include remote data processing solutions in the product definition and define remote data processing. - [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 162 to 174 explain remote data processing as part of the product and clarify that covered functions are not limited to core functionality. ### [Is every cloud service connected to a product part of the CRA product?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#is-every-cloud-service-connected-to-a-product-part-of-the-cra-product) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* No. A cloud or web service is within the CRA product boundary as a remote data processing solution only when the relevant remote processing is at a distance, its absence would prevent the product from performing one of its functions, and the software was designed and developed by or under the responsibility of the manufacturer. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Recitals 11 and 12 and Article 3(2) explain remote data processing and cloud-service boundaries. - [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 168 to 186 provide the three-part RDPS test, website clarification, and third-party SaaS/PaaS/IaaS treatment. ### [Can marketing language determine a product's CRA core functionality?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#can-marketing-language-determine-a-products-cra-core-functionality) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Marketing language is evidence, not the rule. Instructions, promotional and sales materials, manufacturer statements, and technical documentation can all help show intended purpose and context of use, but the actual features and technical capabilities must still match the technical description of the category. 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 124, 127, and 129 explain the evidential role of product materials and misrepresentation risk. - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Annex VII requires technical documentation to describe intended purpose and the conformity-assessment procedure followed. ### [What should manufacturers document about core functionality?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#what-should-manufacturers-document-about-core-functionality) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Document the product boundary, intended purpose, reasonably foreseeable use, selected core functionality, category match or non-match, conformity-assessment route, and the evidence used to reach that view. 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) - Point 128 explains why core functionality should be clearly identified for market-surveillance checking. - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Annex VII lists the technical-documentation content relevant to intended purpose, risk assessment, standards, tests, and conformity route. ### [Does a harmonised standard covering core functionality give full presumption of conformity for the whole product?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#does-a-harmonised-standard-covering-core-functionality-give-full-presumption-of-conformity-for-the-whole-product) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Not automatically. A harmonised standard may support use of internal control for an important class I product where it covers the product's core functionality, but presumption of conformity extends only to the requirements and risks covered by the standard. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 27 and Article 32 address presumption of conformity and 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 133 to 139 and Examples 52 to 55 explain core-functionality standard coverage versus whole-product risk coverage. ### [Can later software or functionality changes alter the core-functionality analysis?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#can-later-software-or-functionality-changes-alter-the-core-functionality-analysis) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Yes, if the change alters the product's intended purpose or affects compliance with the essential cybersecurity requirements. The CRA definition of substantial modification covers changes after placing on the market that affect Annex I Part I compliance or change the intended purpose for which the product was assessed. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 3(30) defines substantial modification by reference to Annex I Part I compliance and intended purpose. - [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 95 to 100 explain software updates, new functionality, foreseen functions, and unassessed risk. ### [Are security updates usually treated differently from feature changes?](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md#are-security-updates-usually-treated-differently-from-feature-changes) *Module: [EU Cyber Resilience Act Core Functionality](/artifacts/eu/cyber-resilience-act/faq/core-functionality.md)* Yes. The draft guidance says security updates are generally not substantial modifications when their primary purpose is to reduce cybersecurity risk, they do not change the product's intended purpose, and they do not introduce new cybersecurity risks. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Recital 39 and Article 3(30) frame when changes are substantial modifications. - [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 101 and related software-update examples distinguish ordinary security updates from changes that introduce new risk or intended purpose. ### [Do repairs, maintenance, or refurbishment automatically count as CRA substantial modifications?](/artifacts/eu/cyber-resilience-act/faq/repairs-and-spare-parts.md#do-repairs-maintenance-or-refurbishment-automatically-count-as-cra-substantial-modifications) *Module: [EU Cyber Resilience Act Repairs and Spare Parts](/artifacts/eu/cyber-resilience-act/faq/repairs-and-spare-parts.md)* No. The CRA definition of substantial modification focuses on changes made after placing on the market that affect compliance with the essential cybersecurity requirements or change the intended purpose for which the product was assessed. Sources for this answer: - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 3(30) defines substantial modification; Recital 42 explains how refurbishment, maintenance, repair, and upgrades should be assessed. - [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 85 to 90 provide draft guidance on applying the substantial-modification concept to physical changes and repairs. ### [How should a physical repair be assessed under the CRA?](/artifacts/eu/cyber-resilience-act/faq/repairs-and-spare-parts.md#how-should-a-physical-repair-be-assessed-under-the-cra) *Module: [EU Cyber Resilience Act Repairs and Spare Parts](/artifacts/eu/cyber-resilience-act/faq/repairs-and-spare-parts.md)* Assess the repair case by case against the product's original CRA assessment. A physical repair is not substantial merely because hardware was opened, a component was replaced, or an old part was exchanged for a newer one. 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 88 to 90 explain that repair and maintenance do not automatically create a substantial modification. - [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj?ref=sorena.io) - Article 3(30) ties substantial modification to Annex I Part I compliance and intended purpose. ## 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: 56 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/55.md) | [Next page](/artifacts/eu/cyber-resilience-act/faq/items/page/57.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/56.md