What the CRA means for products with digital elements

The Cyber Resilience Act explained: requirements and timeline

The Cyber Resilience Act explained: requirements and timeline
  • 19 Nov 2026

The Cyber Resilience Act (CRA) is a European regulation (2024/2847) that sets clear cybersecurity requirements for products with digital elements made available on the EU market. If you supply such products, the CRA affects how you design and develop them, how you manage vulnerabilities and support, and ultimately your access to the EU market.

What does the CRA mean for products with digital elements?

Connected devices and services now play a central role in how we live and work. The CRA therefore sets clear cybersecurity requirements for products with digital elements, from connected devices to software. If you supply these products to the EU market, the CRA determines how you design them, how you report and address vulnerabilities, and what support you provide after launch.

Your first task is clear: determine which products and roles in your supply chain fall within the scope of the CRA and what preparations are needed. Manufacturers, importers and distributors each have different responsibilities, and the regulation affects not only compliance but also product strategy and release planning.

Connected devices and services now play a central role in how we live and work. The Cyber Resilience Act (CRA) sets clear cybersecurity requirements for products with digital elements. If you supply these products to the EU market, the CRA will affect how you design and build products, how you manage vulnerabilities and support, and in the end your access to the market.

You’ll need to decide which products and supply-chain roles are in scope and what preparation you need to carry out.

What is the Cyber Resilience Act?

The CRA, or Regulation (EU) 2024/2847, creates a common European framework for the cybersecurity of hardware and software products. Manufacturers must build cybersecurity into every stage of the product lifecycle, from design and development to vulnerability handling and post-market support.

The Regulation connects these requirements to European product conformity and CE marking. So the CRA is more than an IT or compliance issue. It also shapes product strategy, release decisions, support processes, and your ability to enter and stay in the EU market.

Which companies and products are affected?

The CRA applies to products with digital elements made available on the EU market in the course of a commercial activity. This covers a wide range of hardware, software, separately supplied components, and some related remote data processing solutions.

Some product groups sit wholly or partly outside the CRA because other specific EU legislation applies, for example, medical equipment, motor vehicles, aviation, and marine equipment.

Your obligations also depend on your role in the supply chain. The CRA distinguishes between manufacturers, importers, and distributors, among others. You may be considered a manufacturer if you sell a product under your own name or make substantial modifications to it.

First, determine whether the CRA is relevant to your organisation and which part of your product portfolio the regulation applies to. Then establish your role, the product category and the appropriate conformity route for each product or product family.

What is the CRA timeline?

The CRA takes effect in stages, with three key milestones. Two of these have already passed:

10 December 2024 – entry into force

The CRA entered into force on 10 December 2024. This started the transition period for you to prepare for the obligations.

11 September 2026 – reporting obligations in force

Since 11 September 2026, reporting obligations apply to actively exploited vulnerabilities and severe incidents affecting the security of products with digital elements, including products already on the market.

11 December 2027 – main obligations in force

From 11 December 2027, the main product cybersecurity, conformity, and vulnerability-handling requirements apply.

What steps should you take now to comply with the CRA?

Start by confirming whether you supply products with digital elements to the EU market. Then identify which part of your product portfolio is in scope and group products into practical product families where this makes sense.

For affected products, decide whether you act as a manufacturer, importer, or distributor and which product category applies. These choices define responsibilities, the conformity route, and ownership within your organisation.

Compare your current product development and management practices, including supporting evidence, with the CRA requirements. Focus on secure product development, vulnerability handling, updates and support, and documentation.

Turn the key areas for attention into a realistic plan, prioritising them based on cyber risk, market relevance and planned product changes. Wherever possible, build on your existing product security processes and refine them where needed.

Translate your plan into concrete changes to products and processes. Focus on security in design and development, secure updates, insight into software components through a software bill of materials, and the technical documentation and EU declaration of conformity needed for your chosen conformity route. And make sure vulnerability handling and reporting work in day-to-day practice.

Make responsibilities, decisions, and evidence part of normal product development, release and change processes, supplier management, support, and vulnerability handling. This helps you keep your approach effective as products, components, or risks change.

Frequently asked questions about the Cyber Resilience Act

Does the CRA also apply to products that were already on the market before 2024?

Yes, since 11 September 2026, the reporting obligations for actively exploited vulnerabilities and severe incidents have also applied to products that were already on the EU market. From 11 December 2027, the main cybersecurity and conformity requirements also apply.

What is a software bill of materials and why is it needed under the CRA?

A software bill of materials (SBOM) provides an overview of all software components used in a product, including underlying dependencies. The CRA requires this visibility so that manufacturers can identify and address vulnerabilities in components more quickly.

What happens if my organisation does not comply with the CRA in time?

Non-compliance can restrict access to the EU market, as CE marking under the CRA depends on conformity with the cybersecurity requirements. Start the five steps in good time so that you can meet the main obligations that apply from 11 December 2027.

Preparing for the Cyber Resilience Act?

Find out what the CRA means for your product portfolio and how to prepare for the new cybersecurity requirements.

Questions? Feel free to reach out to us:

Bram van Tiel
Bram van Tiel

Partner cyber, data & technology risk, PwC Netherlands

Peter Avamale
Peter Avamale

Partner cyber, data & technology risk, PwC Netherlands

Follow us