Cybersecurity · Regulation (EU) 2024/2847

Cyber Resilience Act: prepare your products before December 2027

From 11 December 2027, a product with digital elements may be placed on the European market only if it meets the requirements of the Cyber Resilience Act. We help you find out where you stand, then close the gaps.

Engineer's desk: an open connected device, its circuit board and a technical file (computer-generated image).

The subject

Why, and for whom

A vulnerable component is spotted in the inventory, then fixed by an update.

The Cyber Resilience Act (CRA) is a European regulation: it applies directly, without transposition. It covers hardware and software products that connect, directly or indirectly, to another device or to a network, and it binds manufacturers, importers and distributors.

It is not a matter of good practice: it is a condition for placing a product on the market, attested by the CE marking. A first obligation already applies: since 11 September 2026, manufacturers have had to report actively exploited vulnerabilities and severe incidents.

  • Manufacturers of connected products, machinery or software sold in the European Union.
  • Product, quality and R&D managers who have to build the regulation into their development cycle.
  • Importers and distributors who have to verify the compliance of what they sell.

Timeline

Three dates, two of which have already passed.

  1. In force Entry into force

    The regulation is published and begins to take effect.

  2. In force Mandatory reporting

    Actively exploited vulnerabilities and severe incidents must be reported.

  3. Next deadline Full application

    All the requirements apply: without compliance, no placing on the market.

Scope

What the regulation requires

Products that are secure by design
Secure configuration by default, protection of access and data, and no known exploitable vulnerability at the time of placing on the market.
An inventory of components (SBOM)
The list of the software components of the product, kept up to date, so that you know immediately whether a published vulnerability concerns you.
Vulnerability handling
A process for receiving reports, fixing without delay and distributing security updates throughout the support period.
Reporting within set deadlines
Early warning within 24 hours and notification within 72 hours for an actively exploited vulnerability or a severe incident.
Technical documentation
The cybersecurity risk assessment, the design choices and the evidence of compliance, kept at the disposal of the authorities.
A declaration of conformity
The EU declaration of conformity and the CE marking, after an assessment whose procedure depends on the category of the product.

Deliverables

What you receive

  • A qualification note: whether your product is concerned, in which category, and what your role is within the meaning of the regulation.
  • A gap analysis between your situation and the essential requirements, requirement by requirement.
  • A roadmap with the workload estimated, ordered by deadline.
  • The inventory of components (SBOM) and the vulnerability handling process, set up with your teams.
  • The elements of the technical file and the draft EU declaration of conformity.

Process

How the engagement runs

  1. Qualification

    Product concerned or not, category, role: the answer determines everything else.

  2. Gap analysis

    Each requirement is compared with your product and your organisation.

  3. Roadmap

    The gaps are ordered according to the regulation’s deadlines and your schedule for placing on the market.

  4. Bringing into compliance

    Inventory of components, vulnerability handling, design fixes.

  5. File

    Technical documentation and preparation of the declaration of conformity.

Frequently asked questions

What we are asked most often

Is my product concerned by the Cyber Resilience Act?

The regulation covers products with digital elements – hardware or software – whose intended use includes a connection to a device or to a network. Some sectors already covered by their own regulations are excluded, in particular medical devices, motor vehicles and aviation. Qualifying the product is the first step of our support.

What are the deadlines?

The regulation entered into force on 10 December 2024. The reporting obligations have applied since 11 September 2026. All of the requirements apply from 11 December 2027.

What is an SBOM?

It is the inventory of the software components of a product (Software Bill of Materials). It makes it possible to know quickly whether a published vulnerability affects a component you use. The regulation requires the manufacturer to draw it up and keep it up to date.

What penalties are provided for?

Failure to meet the essential requirements can be punished by a fine of up to 15 million euros or 2.5% of worldwide annual turnover, whichever is higher. The authorities can also require the product to be withdrawn from the market.

Does SAOA issue a certification?

No. We prepare your products and your file. Depending on the category of the product, conformity is established by the manufacturer itself or with the involvement of a notified body; we tell you which procedure applies to your case.

This page summarises Regulation (EU) 2024/2847. Only the text published in the Official Journal of the European Union is authoritative. Read the regulation on EUR-Lex.

Let’s talk about what you need.

Describe your situation in a few lines: we will come back to you with a scoping proposal and a fixed-price quote.