Artifact GuideEU

Cyber Resilience Act comparison CRA vs UK PSTI Act

Use separate scope tests and legal evidence for the EU CRA and the UK PSTI product-security regime, even when the same engineering controls support both.

The UK regime has applied since 29 April 2024 to relevant UK consumer connectable products. Most CRA product duties apply from 11 December 2027, with Article 14 reporting from 11 September 2026.

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

The EU Cyber Resilience Act (CRA) and the UK Product Security and Telecommunications Infrastructure (PSTI) product-security regime can both apply to one connected product, but they answer different legal questions. The CRA broadly covers products with digital elements made available on the EU market and imposes lifecycle, conformity, support, vulnerability-handling, and reporting duties. The UK regime applies to relevant connectable products made available to UK consumers, subject to statutory scope conditions and excepted products. It currently specifies three baseline security requirements, generally requires a to accompany the product, subject to the specific Schedule 2A deemed-compliance route, and gives manufacturers, importers, and distributors separate supply-chain duties.

Side-by-side comparison

EU CRA vs UK PSTI product-security regime

Use the matrix to separate product scope, actors, security duties, evidence, dates, and enforcement before reusing technical controls across the EU and UK.

Review all sources
First framework
EU Cyber Resilience Act

Horizontal product-cybersecurity regime for products with digital elements made available on the EU market.

Second framework
UK PSTI Act

Consumer connectable-product security regime under Part 1 of the PSTI Act 2022 and the 2023 Security Requirements Regulations.

Scope boundary

EU Cyber Resilience Act

CRA applies to products with digital elements made available on the Union market whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network. Covered software, hardware, separately placed components, and necessary remote data-processing solutions remain subject to exclusions and special rules.

UK PSTI Act

Covers a relevant connectable product that meets the UK consumer conditions in section 54. A relevant connectable product is an internet-connectable or network-connectable product that is not an excepted product.

Operational implication

Run both tests. CRA can cover non-consumer software and hardware outside PSTI scope; PSTI turns on statutory connectability, UK consumer-market facts, and listed exceptions.

Covered actors

EU Cyber Resilience Act

CRA assigns duties to manufacturers, importers, and distributors; authorised representatives perform tasks under a written mandate. Importers, distributors, or other persons can become manufacturers under Articles 21 and 22. Article 24 gives open-source software stewards a separate, limited set of obligations.

UK PSTI Act

Manufacturers must meet the applicable security requirements and statement duties. Importers and distributors have their own supply and compliance-failure duties: check the accompanying statement or, where Schedule 2A applies, be satisfied that the specified conditions are met.

Operational implication

Map the legal entity and role in each market. Shared corporate ownership does not make the EU manufacturer, EU importer, UK manufacturer, and UK importer the same legal actor.

Required security work

EU Cyber Resilience Act

CRA manufacturers must address Annex I product-security and vulnerability-handling requirements through risk-based design, development, production, maintenance, vulnerability remediation, security updates, component documentation, and required user information throughout the applicable support period.

UK PSTI Act

The current specified requirements cover passwords, publication of a vulnerability-reporting route and response times, and publication of a minimum security-update period with an end date. Schedule 2 specifies security-requirement deemed-compliance routes; Schedule 2A separately governs deemed compliance with the manufacturer statement-accompaniment duty.

Operational implication

Reuse test and process evidence only after mapping it to the exact CRA requirement and UK Schedule 1 requirement. Keep the CRA conformity artifacts and UK separate.

Application dates

EU Cyber Resilience Act

CRA Chapter IV applies from 11 June 2026, Article 14 reporting applies from 11 September 2026, and the general application date is 11 December 2027. Under Article 69, products placed on the market before 11 December 2027 are generally subject to the other requirements only if substantially modified from that date; Article 14 reporting also covers earlier in-scope products.

UK PSTI Act

The UK product-security regime came into force on 29 April 2024. The 2025 vehicle exceptions took effect on 25 February 2025, and further deemed-compliance amendments took effect on 4 December 2025.

Operational implication

Use 29 April 2024 for current UK supply decisions. Use the CRA's staged dates only for EU duties, and check later UK amendments when relying on an exception or deemed-compliance route.

Evidence record

EU Cyber Resilience Act

CRA records include the cybersecurity risk assessment, Annex I mapping, vulnerability-handling process, software bill of materials, support-period rationale, test results, technical documentation, conformity-assessment records, EU declaration of conformity, and CE-marking evidence. Retention periods and responsibilities follow the applicable operator duty.

UK PSTI Act

Where required, the manufacturer prepares the Schedule 4 statement and it accompanies the product; manufacturers and importers retain it for the longer of 10 years from issue or the defined support period. Schedule 2A treats section 9(2) as met for a current, unexpired Japan JC-STAR STAR-1 conformance label or a current, unexpired Singapore Cybersecurity Labelling Scheme label at any level. Sections 15(5) and 22(3) require importers and distributors to be satisfied that those conditions are met; section 15(5) also disapplies importer statement retention on that route.

Operational implication

A CRA declaration or CE mark does not replace the UK statement. The UK statement is also not a CRA conformity assessment or third-party approval.

Enforcement exposure

EU Cyber Resilience Act

CRA enforcement can involve market-surveillance authorities, corrective action, restriction or withdrawal of products, and administrative fines under the CRA enforcement framework.

UK PSTI Act

OPSS can use information, compliance, stop, and recall measures and monetary penalties. The statutory penalty maximum is the greater of GBP 10 million and 4% of qualifying worldwide revenue, subject to the Act's calculation rules.

Operational implication

Treat both regimes as enforceable product laws. The UK figure is a statutory maximum, not an automatic fine or a prediction for a particular breach.

Which legal sources to use

EU Cyber Resilience Act

Use CRA sources when the decision turns on EU scope, Annex I requirements, vulnerability handling, support period, Article 14 reporting, technical documentation, conformity assessment, EU declaration of conformity, CE marking, or CRA enforcement.

UK PSTI Act

Use the PSTI Act, the revised 2023 Regulations, and current OPSS or DSIT guidance for UK scope, requirements, statements, actors, dates, penalties, and enforcement powers.

Operational implication

Build shared product-security controls, then issue separate EU CRA and UK PSTI conclusions with their own evidence indexes, responsible actors, and release gates.

Overlap and reuse

EU Cyber Resilience Act

CRA Annex I covers controls such as secure credentials and configuration, vulnerability handling, security updates, and user security information. These can share engineering evidence with the UK baseline, while the CRA also requires broader risk, lifecycle, technical-documentation, and conformity work.

UK PSTI Act

PSTI overlaps technically through credentials, vulnerability reporting, and update-support information, but its current statutory baseline is narrower than the CRA lifecycle and conformity framework.

Operational implication

Reuse a control only where the evidence satisfies both mapped requirements. Do not infer PSTI scope from CRA scope, infer CRA conformity from the three UK requirements, or use either regime's declaration as the other's legal artifact.

Practical decision rule

EU Cyber Resilience Act

Apply Article 2 scope and exclusions, identify the economic operator and product category, and use Articles 69 and 71 for the applicable transition and date. Then map Annex I requirements, support, Article 14 reporting, technical documentation, conformity assessment, declaration, and CE marking for that product and actor.

UK PSTI Act

If the item is a relevant connectable product, apply the section 54 UK consumer test and Schedule 3 exceptions. Then identify the actors, security requirements, statement or Schedule 2A route, applicable retention, and compliance-failure duties.

Operational implication

Record separate pass or fail decisions for EU CRA scope and UK PSTI scope. A dual-market release needs both evidence indexes when both tests pass.

Practical decision rule

How to use this comparison

  • Use the CRA column as the cited EU work plan for products with digital elements.
  • Use the UK PSTI column to test connectability, UK consumer-market status, exceptions, actors, the three specified requirements, the , and supply-chain duties.
  • Reuse engineering controls where they genuinely overlap: credentials, vulnerability disclosure, updates, secure configuration, dependency tracking, and support-period communication.
  • Keep the CRA technical documentation and declaration separate from the UK , even where both cite the same test or control evidence.
Section 1

Start with two separate scope tests

For the CRA, ask whether a software or hardware product, separately placed component, or necessary remote data-processing solution is a product with digital elements made available on the Union market whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network. Then check the CRA's exclusions and special rules. A consumer purpose or internet connection is not required in every CRA case.

For UK PSTI, ask whether the item is an internet-connectable or network-connectable product under sections 4 and 5 of the Act, whether it is or will be a under section 54, and whether Schedule 3 to the 2023 Regulations excepts it. The government guidance lists medical devices, smart meter products, electric-vehicle charge points, certain computers without cellular connectivity, specified Northern Ireland supplies, and, since 25 February 2025, specified vehicle categories among the exclusions or exceptions. Apply the exact legal conditions rather than relying on those labels alone.

  • A business-only product can still be a when identical products are also made available to UK consumers and the section 54 conditions are met.
  • A general-purpose software product may enter CRA scope but not UK PSTI scope because the UK definition turns on a connectable product and the consumer-market conditions.
  • A cellular tablet or a computer designed exclusively for children under 14 does not fall within the specific non-cellular computer exception described in the UK guidance.
  • Record the scope conclusion, excluded-product analysis, intended markets, and first supply or market-placement facts for each product.
Recommended next step

Separate CRA evidence from UK PSTI evidence

Use separate scope decisions, actor maps, and evidence indexes for the EU CRA and UK PSTI regime, then link any shared test or control to the requirement it supports in each market.

Section 2

What each manufacturer must do

A CRA manufacturer must connect its cybersecurity risk assessment to the Annex I product-security and vulnerability-handling requirements, establish a support period, prepare technical documentation, complete the applicable conformity assessment, issue an EU declaration of conformity, affix CE marking, provide required user information, and meet the CRA's reporting and cooperation duties.

A UK PSTI manufacturer must meet the applicable Schedule 1 security requirements. Passwords must meet the specified unique-per-product or user-defined rules. The manufacturer must publish, free of charge and without prior request, clear English information on how to report security issues and the expected acknowledgement and status-update times. It must also publish the minimum security-update period, including an end date, in clear English that a non-technical reader can understand.

Before making an in-scope product available in the UK, the manufacturer generally must ensure that a accompanies it. The statement contains the Schedule 4 information and may be digital if it still accompanies the product and meets the legal requirements. Schedule 2 provides routes for deemed compliance with the security requirements; using one does not by itself remove the statement duty. Regulation 4A and Schedule 2A separately treat section 9(2) as met when the product has a current, unexpired Japan JC-STAR STAR-1 conformance label or a current, unexpired label at any level of the Singapore Cybersecurity Labelling Scheme. Importers and distributors relying on that route must be satisfied that its conditions are met under sections 15(5) and 22(3).

  • CRA evidence: risk assessment, Annex I mapping, vulnerability-handling records, component information including an SBOM where required, support-period rationale, tests, technical documentation, conformity decision, declaration, CE marking, and Article 14 reporting process.
  • UK PSTI evidence: product-scope analysis, Schedule 1 control evidence, published vulnerability-reporting information, published security-update end date, , supply-chain checks, and records of any compliance failure and response.
  • UK statement retention: where a statement is required, manufacturers and importers keep a copy for the longer of 10 years from issue or the defined support period. Section 15(5) disapplies the importer statement and retention duties where the specified deemed-compliance route applies and the importer is satisfied that its conditions are met.
  • Do not state that the UK rules require security updates for a fixed statutory minimum duration. They require the manufacturer to define and publish the minimum period; other legal or contractual duties may affect what duration is adequate.
Section 3

Supply-chain and enforcement differences

Both regimes assign duties beyond the manufacturer, but the checks and documents differ. CRA importers and distributors verify specified CRA conformity and traceability matters and must respond to suspected non-conformity. Under PSTI, importers and distributors generally must not make an in-scope product available unless the required statement accompanies it. Under sections 15(5) and 22(3), where the Schedule 2A route applies, they must instead be satisfied that its conditions are met. The Act also sets investigation, notification, remediation, prevention, and record duties for compliance failures.

EU market-surveillance authorities enforce the CRA. In the UK, the Office for Product Safety and Standards (OPSS) enforces the PSTI product-security regime. UK powers include compliance, stop, and recall notices, information requirements, and monetary penalties. The statutory maximum for a penalty is the greater of GBP 10 million and 4% of qualifying worldwide revenue, subject to the Act's calculation rules; that is a maximum, not an automatic fine.

  • Share technical evidence for credentials, vulnerability intake, update delivery, secure configuration, dependency tracking, and support commitments where it proves the relevant requirement.
  • Keep legal outputs separate: a CRA technical file, EU declaration, and CE mark do not replace the UK .
  • Keep incident and defect workflows separate: CRA Article 14 notifications follow the CRA triggers and reporting platform, while PSTI compliance-failure duties follow the UK Act.
  • Name the manufacturer, importer, distributor, and any authorised representative for each market; do not assume that one entity has the same legal role in both regimes.
Section 4

Practical dual-market approach

Start with one product-security baseline, then create separate EU and UK evidence indexes. Shared tests can reduce duplicate engineering work, but every legal conclusion must point to the correct instrument and actor.

The UK regime has applied since 29 April 2024. CRA Article 14 reporting applies from 11 September 2026, and most CRA product and conformity duties apply from 11 December 2027. Under Article 69, products placed on the market before 11 December 2027 are generally subject to the other requirements only if substantially modified from that date; Article 14 reporting also covers earlier in-scope products. Use the actual supply, placement, modification, and reporting facts rather than the model's original launch date.

  • Create one security-control register for credentials, updates, vulnerability disclosure, secure configuration, dependency tracking, and support commitments.
  • Create a CRA evidence index for Annex I mappings, support-period rationale, SBOM or dependency evidence, test results, technical documentation, conformity documents, and reporting readiness.
  • Create a UK PSTI evidence index for scope, exceptions, actor roles, password design, vulnerability-reporting publication, security-update end date, , retention, and compliance-failure handling.
  • Release to each market only after that market's scope, actor, date, evidence, and accompanying-document checks are complete.
Primary sources

References and citations

eur-lex.europa.eu20 citations
Referenced sections
  • Primary source for CRA scope, economic-operator duties, Annex I cybersecurity requirements, technical documentation, conformity assessment, CE marking, Article 14 reporting, staged application, market surveillance, and penalties.
  • Binding EU source for CRA scope.
  • Shows why CRA scope must be assessed under EU product-cybersecurity rules.
Show 17 more
  • Primary source for CRA product scope and products with digital elements.
  • Articles 13 and 18 to 24 distinguish manufacturers, representatives, importers, distributors, persons assuming manufacturer duties, and open-source software stewards.
  • Supports keeping a CRA-specific Annex I mapping.
  • Article 13 and Annex I set risk-based product-security and vulnerability-handling duties.
  • Supports separating CRA conformity evidence from other regulatory evidence.
  • Binding EU source for 11 June 2026, 11 September 2026, and 11 December 2027 CRA dates.
  • Sets the staged application dates for the CRA requirements in the EU column.
  • Primary source for CRA staged application dates.
  • Article 13 and Annex VII specify manufacturer evidence, technical documentation, conformity outputs, and record retention.
  • Binding EU source for CRA enforcement exposure.
  • Supports the CRA corrective and restrictive measures described in the EU column.
  • Primary source for CRA market surveillance, corrective actions, restrictions, withdrawals, and penalties.
  • Binding EU source for CRA legal conclusions.
  • Primary source for CRA decisions listed in the EU column.
  • Annex I supplies the shared technical controls; Articles 13 and 31 to 34 add lifecycle and conformity requirements.
  • Articles 2, 13, 14, 19 to 24, 69 and 71 govern the scope, role, duty and timing sequence.
  • Primary source for the CRA side of the decision rule.
"horizontal cybersecurity requirements for products with digital elements"
More quoted passages
"products with digital elements"
"Annex I"
"CE marking"
"Article 14 shall apply from 11 September 2026"
"Chapter IV"
"This Regulation shall apply from 11 December 2027"
"penalties"
"corrective actions"
"market surveillance"
"horizontal cybersecurity requirements"
legislation.gov.uk9 citations
Referenced sections
  • Binding UK source for the security requirements, exceptions, statement contents and retention, commencement date, and deemed-compliance provisions as amended.
  • Binding source for Schedule 1 security requirements, Schedule 4 statement information, and deemed-compliance provisions.
  • Regulation 1 gives the 29 April 2024 commencement date and the revised text records later amendments.
Show 6 more
  • Regulations 7 to 9 and the schedules govern statement information and retention.
  • Current revised text for the specified requirements, exceptions, statements, retention, and deemed-compliance provisions.
  • Binding source for the three specified security requirements.
  • Binding source for the current UK requirements and evidence duties.
  • Binding source for exceptions, security requirements, statements, and retention.
  • Primary source for current UK requirements, exceptions, statement details, retention, and deemed compliance.
gov.uk6 citations
Referenced sections
  • Official guidance on current scope examples and exceptions, actor roles, the three security requirements, statements of compliance, OPSS enforcement, and the vehicle exceptions effective from 25 February 2025.
  • Official guidance listing current scope examples and excluded or excepted product categories.
  • Explains that the statement may be digital if it accompanies the product and satisfies the legal requirements.
Show 3 more
  • Supports the separate UK evidence and actor checks.
  • Explains the operational UK control and statement requirements.
  • Supports the practical UK scope, requirement, and statement checks.
legislation.gov.uk4 citations
Referenced sections
  • Binding UK source for connectable-product and consumer-market scope, manufacturer, importer and distributor duties, statements of compliance, compliance failures, enforcement powers, and the monetary-penalty maximum.
  • Sections 4, 5 and 54 establish the relevant-connectable-product and UK-consumer scope tests.
  • Binding source for the UK scope and actor sequence.
Show 1 more
  • Primary source for the UK scope, actor, statement, compliance-failure, and enforcement checks.
etsi.org2 citations
Referenced sections
  • Technical context for shared consumer IoT controls. The UK duties on this page are grounded in the PSTI Act and Regulations, not in the standard alone.
  • Supports using consumer IoT controls as technical overlap context.
"Cyber security provisions for consumer IoT"
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Supports treating CE marking as a CRA/EU compliance signal.
  • Commission overview states that products will bear CE marking to indicate compliance with CRA requirements.
"comply with the CRA requirements"
More quoted passages
"CE marking"
legislation.gov.uk2 citations
Referenced sections
  • Sets the duties of relevant persons and authorised representatives.
  • Binding source for manufacturer, importer, distributor, authorised-representative, statement, investigation, notification, remediation, and record duties.
legislation.gov.uk2 citations
Referenced sections
  • Binding source for connectability, consumer-market, actor, and supply definitions.
  • Binding source for product scope and supply-chain duties.
legislation.gov.uk
Referenced sections
  • Primary source for UK PSTI legal conclusions.
Show all related guides (55)

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

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 Conformity Assessment Routes FAQ | Module A, Module B+C, Module H, Important and Critical Products

Cyber Resilience Act FAQ on when manufacturers can use module A, when module B+C or module H is required, and how important and critical products affect the route.

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.

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.