The Cyber Resilience Act (Regulation (EU) 2024/2847), which entered into force on 10 December 2024, is being implemented in phases and is fundamentally changing the rules for digital products on the European market. While the regulation will generally apply from 11 December 2027, important initial phases are already in effect. Chapter IV (Articles 35 to 51), governing the notification of conformity assessment bodies, has been in effect since 11 June 2026, and the mandatory reporting obligations under Article 14 have applied since 11 September 2026. The legislation introduces mandatory end-to-end cybersecurity compliance throughout the entire lifecycle of a product, from design and development to operations. It also establishes new prerequisites for CE marking, which will be a mandatory requirement for placing any regulated digital product on the EU market.

Scope

The CRA covers a wide variety of products with digital elements. This includes connected hardware devices and their physical components, as well as standalone software, firmware, and software components. It also covers Remote Data Processing Solutions (RDPS), i.e., processing software designed by or under the responsibility of the manufacturer, without which the product could not perform one of its functions.

Standalone services, including SaaS offerings not forming part of a product’s remote data processing solution, generally fall outside the CRA. Their providers may nevertheless be subject to other cybersecurity rules, including the NIS2 where applicable. Specific categories of products governed by sector-specific rules, including medical devices and in vitro diagnostic medical devices, civil aviation equipment, motor vehicles, and marine equipment, are also explicitly excluded. Further exclusions apply to spare parts supplied solely to replace identical components and to free and open-source software developed or supplied outside the course of a commercial activity.

Products within the scope of the legislation are divided into categories: default products, important products (Class I and Class II) and critical products. The category determines the applicable conformity assessment route, and the detailed technical descriptions of important and critical products are set out in Commission Implementing Regulation (EU) 2025/2392.

Significance and Impact on Business

This new legal framework is highly significant for both the technology and business sectors, introducing extensive new obligations and severe penalties. Manufacturers must determine a support period reflecting the product’s expected use, normally of at least five years (or the shorter expected use period) and provide security updates during this period free of charge (unless otherwise agreed upon with a business user for a tailor-made product) and, where technically feasible, separately from functionality updates. Furthermore, released security updates must remain available for download for at least 10 years after each update is issued or for the remainder of the support period, whichever is longer.

Beyond determining the support period, the core of the CRA lies in the manufacturer’s obligations under Article 13. Manufacturers must, for example, design, develop and produce their products in accordance with the essential cybersecurity requirements set out in Annex I (e.g., making products available without known exploitable vulnerabilities, with a secure-by-default configuration, protection against unauthorised access and protection of data, including encryption where appropriate), carry out and document a cybersecurity risk assessment and update it as appropriate during the support period, exercise due diligence when integrating third-party components, including free and open-source components, and put in place vulnerability handling processes, including drawing up a software bill of materials (SBOM). They must also draw up the technical documentation, carry out the applicable conformity assessment procedure and provide users with clear information and instructions.

In addition, Article 14 imposes reporting obligations which, unlike most of the CRA, have already applied since 11 September 2026, and do so also for legacy products, i.e., products placed on the market before 11 December 2027. Manufacturers must notify any actively exploited vulnerability contained in their product and any severe incident having an impact on its security. Notifications are submitted simultaneously to the CSIRT designated as coordinator and to ENISA via the single reporting platform, in three stages:

  • an early warning without undue delay and in any event within 24 hours of the manufacturer becoming aware of the vulnerability or incident;
  • a vulnerability or incident notification with more detailed information without undue delay and in any event within 72 hours of the manufacturer becoming aware of it; and
  • a final report no later than 14 days after a corrective or mitigating measure is available (for vulnerabilities), or within one month after the submission of the incident notification (for severe incidents).

Importantly, the manufacturer’s obligations are not limited to the original manufacturer. Under Article 21, an importer or distributor is considered a manufacturer, and becomes subject to the obligations under Articles 13 and 14, if it places a product on the market under its own name or trademark (white-labelling or rebranding) or carries out a substantial modification of a product already placed on the market. Under Article 22, the same applies to any other person who substantially modifies a product and makes it available on the market. Under Article 3(30), a “substantial modification” is a change to a product after it is placed on the market that affects its compliance with the essential cybersecurity requirements or modifies the intended purpose for which it was assessed. Indicators include changes not foreseen in the manufacturer’s original risk assessment or changes expanding the product’s attack surface. A substantial modification generally triggers a new conformity assessment for the affected part or, where relevant, the product as a whole, whereas standard security updates and patches that reduce cybersecurity risk without changing the intended purpose are generally not considered substantial modifications.

The consequences of non-compliance are structured under a tiered system of fines. Breaches of the essential cybersecurity requirements (Annex I) and of the manufacturer’s obligations under Articles 13 and 14 described above may result in fines of up to EUR 15 million or 2.5% of total worldwide annual turnover, whichever is higher. Breaches of other obligations under the CRA, notably those of importers, distributors and authorised representatives, may result in fines of up to EUR 10 million or 2% of turnover, whichever is higher. Supplying incorrect, incomplete or misleading information to notified bodies or market surveillance authorities may result in a fine of up to EUR 5 million or 1% of turnover, whichever is higher. However, under Article 64(10), microenterprises and small manufacturers are exempt from administrative fines for missing the 24-hour early-warning deadline, and open-source software stewards are exempt from administrative fines for infringements of the CRA.

Compliance Roadmap and European Commission Guidance

To navigate these new rules successfully, manufacturers must follow a structured conformity assessment process before affixing the CE mark. This includes identifying the applicable requirements, determining the appropriate route to conformity (internal control, or third-party assessment in the form of EU-type examination, or full quality assurance), verifying compliance through rigorous testing, and compiling comprehensive technical documentation. The process concludes with the EU declaration of conformity and the affixing of the CE marking.

A significant strategic advantage for businesses will be the application of harmonised standards, including the EN 40000 series, which are currently being developed by CEN/CENELEC and ETSI under the European Commission’s standardisation request. The first drafts of product-specific standards were delivered in 2026 and further standards will follow in 2027. Once their references are published in the Official Journal of the EU, applying these standards will confer a presumption of conformity for the requirements they cover. For important Class I products, applying the applicable standards to the relevant requirements may also enable the internal-control (self-assessment) route under Article 32(2).

Furthermore, to assist companies with this transition, the European Commission published its non-binding guidance on the application of the CRA on 27 July 2026. The document serves as a practical compliance playbook, featuring 67 practical examples to help businesses navigate complex CRA scenarios. It provides detailed clarifications of the scope regarding grey areas such as Remote Data Processing Solutions (RDPS) and free and open-source software (FOSS), as well as guidance on substantial modifications, support periods, cybersecurity risk assessments and reporting obligations. Crucially, the guidance takes an SME-friendly approach, focusing on proportionate compliance for micro, small, and medium-sized enterprises.

CRA Implementation in the Czech Republic

Although the CRA is directly applicable in all Member States, it requires national implementing rules. In July 2026, the Ministry of Industry and Trade (MPO) presented the draft Act on Cybersecurity Requirements for Products with Digital Elements, which is currently pending in the legislative process. The draft establishes the national market surveillance architecture and defines the inspection powers of the competent authorities. It also covers the designation of the notifying authority and the regulation of notified conformity assessment bodies, and sets out the national rules on administrative offences and penalties.

In the Czech Republic, the National Cyber and Information Security Agency (NÚKIB) acts as the national coordinator for the purposes of the reporting obligations under Article 14 described above.

Practical Takeaways

While the December 2027 deadline may seem far away, some obligations already apply and businesses should start preparing now. In summary:

  • Reporting processes for actively exploited vulnerabilities and severe incidents should already be in place, as the Article 14 obligations have applied since September 2026, including on legacy products.
  • Manufacturers should map their products against the essential requirements of Annex I, establish a documented cybersecurity risk assessment and vulnerability handling (including an SBOM) and determine the applicable conformity assessment route.
  • Businesses should review supplier agreements and cybersecurity due diligence and assess their exposure to regulatory and product liability risks. In addition, the revised Product Liability Directive (EU) 2024/2853, which applies to products placed on the market or put into service after 8 December 2026, expressly covers defective software and includes compensation for the destruction or corruption of data not used for professional purposes.
  • Importers and distributors should check whether rebranding or substantial modification makes them manufacturers under Article 21; other persons who substantially modify a product and make it available on the market may also assume obligations under Article 22.
  • Any change to a product already on the market should be screened as to whether it amounts to a substantial modification triggering a new conformity assessment; ordinary security patches generally do not.
  • Under Article 23, economic operators must, on request, identify the economic operators from whom they received a product and, where available, those to whom they supplied it. The relevant names and addresses must be available for 10 years after receipt or supply, respectively.

Proactive preparation and early alignment with the upcoming standards will be essential for businesses to maintain uninterrupted access to the EU market and mitigate severe regulatory and liability risks in the years ahead.

Author