- Supports the general EU product-law meaning of CE marking as a manufacturer declaration, not a country-of-origin mark.
"not a mark of origin"
Straight answers to the CRA questions that decide whether a product can be placed on the EU market and what evidence must exist before launch.
Use this page to orient product, engineering, security, compliance, legal, importer, distributor, and market-access reviews.
Structured answer sets in this page tree.
Cited legal and guidance references.
The EU Cyber Resilience Act applies horizontal cybersecurity rules to products with digital elements. This FAQ summarizes the core market-access questions: what is in scope, who carries each role, what manufacturers must build and document, when vulnerability reports are triggered, how conformity assessment and CE marking work, how long support must last, and what market surveillance authorities can check.
These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.
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.
Practical CRA CE marking answers for products with digital elements: conformity assessment, EU declaration, technical documentation, standards, software placement, and launch evidence.
Cyber Resilience Act FAQ on manufacturer due diligence for integrated components, third-party software, FOSS dependencies, SBOMs, vulnerability handling, and evidence records.
Cyber Resilience Act FAQ on when manufacturers can use module A, when module B+C or module H is required, and how important and critical products affect the route.
CRA FAQ on Article 13 cybersecurity risk assessments, Annex I applicability, intended purpose, foreseeable use, technical documentation, and update evidence.
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 FAQ on economic-operator roles: manufacturers, importers, distributors, authorised representatives, substantial modification, traceability, and evidence controls.
CRA FAQ on Annex I product cybersecurity requirements, vulnerability handling, secure-by-default design, risk assessment, documentation, lifecycle duties, and user information.
FAQ on Cyber Resilience Act hardware and software boundaries: combined products, standalone software, source code, components, remote data processing, SaaS and market-placement changes.
Cyber Resilience Act FAQ on how harmonised standards, common specifications, certification schemes, and OJ publication affect CRA conformity evidence.
FAQ on CRA important and critical products, Annex III and Annex IV classification, core functionality, and conformity assessment consequences.
Cyber Resilience Act FAQ on integrated components, third-party software, remote data processing, SBOM-style evidence, upstream fixes, FOSS dependencies, and manufacturer responsibility.
Grounded CRA FAQ on overlap with the Radio Equipment Directive, Machinery Regulation, GPSR, Data Act, exclusions, declarations, documentation, and existing certificates.
FAQ for Cyber Resilience Act launch decisions: known exploitable vulnerabilities, CVEs, component flaws, secure-by-default settings, release gates, Article 14 reporting, and evidence.
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.
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.
Cyber Resilience Act FAQ on market-surveillance authorities, investigations, corrective action, withdrawal, recall, safeguards, sweeps, documentation access, and penalties.
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 explaining the full-quality-assurance route, notified-body assessment, quality-system scope, technical documentation, CE marking, declarations, and records.
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.
Cyber Resilience Act FAQ for free and open-source software: commercial activity, steward duties, manufacturer due diligence, vulnerability handling, public documentation, and user obligations.
Cyber Resilience Act FAQ on OTA updates, automatic security updates, secure update distribution, support-period evidence, and offline update paths.
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 FAQ on product families, variant grouping, shared technical documentation, conformity evidence, and when cybersecurity-relevant differences need separate assessment.
EU Cyber Resilience Act FAQ on products with digital elements, software, firmware, remote data processing, components, exclusions, market placement, and CRA operator 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.
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.
Cyber Resilience Act FAQ on secure-by-default configuration, automatic security updates, attack surface reduction, authentication, data minimisation, user information, and tailor-made products.
Cyber Resilience Act FAQ on classifying security updates, functionality updates, support-period duties, automatic updates, user notices, and substantial-modification review.
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.
Practical CRA FAQ on how manufacturers determine support periods, disclose support end dates, keep security updates available, and document support-period 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 FAQ explaining Annex VII technical documentation, risk assessment evidence, conformity assessment files, vulnerability handling records, product families, RDPS, language, and authority access.
CRA FAQ on the transition period covering entry into force, 2026 reporting, 2027 application, legacy products, stock, customs timing, and software versions.
FAQ on CRA security-update availability, support-period notices, optional public software archives, historical versions, and Article 13(10) software-version limits.
Practical CRA FAQ on Annex II user instructions, support-period disclosure, vulnerability contacts, update notices, importer and distributor information.
Practical CRA FAQ on vulnerability handling: SBOMs, remediation, coordinated disclosure, component issues, security updates, support periods, Article 14 reporting, and user notices.
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.
CRA FAQ on core functionality, product boundaries, remote data processing, integrated components, ancillary functions, and software changes that affect product classification.
CRA FAQ for repairs, spare parts, legacy products, security updates, substantial modification, and responsibility after product changes.
A product is in CRA scope when it is a product with digital elements, is made available on the EU market, and its intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network.
Products with digital elements include software or hardware products and their remote data processing solutions, including software or hardware components placed on the market separately. The scope check still needs the Article 2 exclusions, such as certain products already covered by specified Union product regimes, and the national security or defence exclusion.
The CRA splits essential cybersecurity requirements into product properties and vulnerability-handling processes. Manufacturers must design, develop, and produce products in line with Annex I Part I and must operate vulnerability handling in line with Annex I Part II throughout the support period.
The product-property requirements are applied through the manufacturer's cybersecurity risk assessment. If a Part I requirement is not applicable to the product, the manufacturer must justify that in the technical documentation. The vulnerability-handling requirements are not just launch checks; they continue during the support period.
Manufacturers must notify actively exploited vulnerabilities contained in a product with digital elements and severe incidents having an impact on the security of that product. Notification is made via the single reporting platform to the CSIRT designated as coordinator and to ENISA.
An actively exploited vulnerability requires reliable evidence that a malicious actor exploited the vulnerability. A zero-day vulnerability is reportable when that condition is met, but a vulnerability found through good-faith testing without evidence of malicious exploitation is not automatically a mandatory Article 14 report.
Conformity assessment is the legal procedure used to demonstrate that the product and the manufacturer's vulnerability-handling processes meet the CRA's essential requirements. The CRA routes are Module A internal control, Module B plus C EU-type examination with conformity to type, and Module H full quality assurance.
The default category can generally use Module A. Important and critical products may need a notified body, depending on the class, whether harmonised standards are applied, and whether another route such as a European cybersecurity certification scheme becomes mandatory for critical products.
CE marking is the manufacturer's visible declaration that the product complies with applicable EU harmonisation legislation, including the CRA where it applies. It is not a mark of origin and does not mean a product was made in the EU.
Under the CRA, the manufacturer affixes the CE marking only after the relevant conformity assessment has a positive result, the EU declaration of conformity is drawn up, and the product satisfies the applicable requirements. Software products also need CE marking, either on the EU declaration of conformity or on the website accompanying the software product.
The manufacturer must determine the support period when placing the product on the market and must handle vulnerabilities effectively during that period. The period must reflect the expected use time, reasonable user expectations, product nature and intended purpose, relevant Union law, comparable products, operating environment availability, and support periods of core third-party components.
The CRA sets a support period of at least five years unless the product is expected to be in use for less than five years; in that case the support period must correspond to the expected use time. The end date, including at least the month and year, must be clearly available at purchase.
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.
Convert CRA scope, role, support-period, and conformity questions into evidence requests and review tasks.
Review product boundaries, launch blockers, vulnerability-handling evidence, and market-access records with the Sorena team.
"not a mark of origin"
"market surveillance"
"kept at the disposal of market surveillance authorities"
"Products will bear the CE marking"