Skip to content
SynergyBit
Knowledge hub

What is the Cyber Resilience Act

A clear overview of what CRA means for manufacturers, importers and distributors of products with digital elements.

01

CRA in a nutshell

The Cyber Resilience Act (Regulation of the European Parliament and of the Council EU 2024/2847) is the first European law to set mandatory cybersecurity requirements for products with digital elements across their entire lifecycle.

The aim is for both hardware and software placed on the EU market to be more secure by design, to receive security updates, and for customers to have enough information to use the product safely.

02

Who CRA affects

CRA affects almost all products with digital elements – physical devices that can connect to a network, IoT and standalone software. Areas covered by other sector-specific law remain outside its scope, for example certain medical devices, aviation or cars.

Obligations fall on manufacturers, but importers and distributors have their roles too. An importer must verify that the manufacturer has met its obligations; a distributor must act with due care. Whoever substantially modifies a product or places it on the market under their own brand may take on the manufacturer's obligations.

03

Why it is important to start early

CRA compliance is not a one-off task. It requires security built into the design, a risk assessment, vulnerability management throughout the support period and complete documentation. That cannot be done at the last minute.

On top of that, reporting obligations start before full compliance – already from 11 September 2026. Preparation should therefore be ongoing, not a final sprint before the deadline.

Main manufacturer obligations under CRA

01

Security by design

Design, develop and manufacture products so they ensure an appropriate level of cybersecurity relative to the risks.

02

Cybersecurity risk assessment

Carry out and document a risk assessment and reflect its results across all phases of the product lifecycle.

03

Vulnerability management

Effectively address vulnerabilities during the support period, provide security updates and maintain an SBOM.

04

Incident reporting

Report actively exploited vulnerabilities and severe incidents to ENISA within set deadlines (from 11 Sep 2026).

05

Technical documentation

Prepare and maintain technical documentation demonstrating compliance with CRA requirements.

06

Conformity assessment and CE

Carry out conformity assessment, issue the EU declaration of conformity and affix the CE marking.

07

Information for users

Provide users with clear information and instructions for using the product securely.

08

Support period

Define and maintain a product support period – generally at least five years, depending on the expected product lifetime.

Product categories and conformity assessment

CRA classifies products by level of risk. The category determines whether an internal self-assessment is sufficient or a notified body must be involved.

  1. Default category

    Most products. Conformity assessment can usually be done internally as a self-assessment.

  2. Important products – class I

    Higher risk (e.g. password managers, VPNs, network elements). Requires applying harmonised standards or involving a notified body.

  3. Important products – class II

    Even higher risk (e.g. firewalls, intrusion detection systems). Assessment by a notified body is generally required.

  4. Critical products

    The most sensitive category with the strictest requirements, where European certification may also be required.

Frequently asked questions about CRA

From when do we have to comply with CRA?
The main CRA requirements apply from 11 December 2027. However, the reporting obligations for vulnerabilities and incidents start earlier – from 11 September 2026.
What penalties apply for non-compliance?
Breaching key obligations can attract fines of up to EUR 15 million, or 2.5% of global annual turnover – whichever is higher.
Does CRA also apply to free open-source software?
CRA introduces a special, lighter regime for open-source software. It depends on whether a commercial activity is involved. We are happy to assess the specific impact for your situation.
What is an SBOM and why does CRA require it?
An SBOM (Software Bill of Materials) is an inventory of the components a product is made of. It makes it possible to quickly determine whether a newly discovered vulnerability in a component affects you.

Start with CRA before the deadline catches up with you

A free consultation will quickly show you where you stand and the shortest path to compliance.

Book a consultation