Skip to main content
Exostruction
Back to overview
Juljan Blischke4 min read

Cyber Resilience Act: What Software Buyers Need to Know Now

The Cyber Resilience Act brings reporting duties and product obligations for software. Deadlines, scope and what SMEs should prepare now.

Guide
Cyber Resilience Act: What Software Buyers Need to Know Now

In short: The Cyber Resilience Act (CRA) makes the security of software and connected products a legal requirement in the EU. Since September 11, 2026, reporting duties apply for actively exploited vulnerabilities and severe security incidents, and the core obligations follow on December 11, 2027. You will find the key deadlines and a preparation checklist below.

The CRA is not a topic for later: the reporting channel has had to be in place since September, and the product obligations apply in December 2027.

What the Cyber Resilience Act Regulates

The CRA entered into force on December 10, 2024 and creates a single EU framework for the cybersecurity of products with digital elements. This covers software products, connected hardware and software or hardware components that are placed on the market separately. Cybersecurity thus moves from a voluntary quality question to a duty of proof: manufacturers must be able to show that security was considered across the entire product lifecycle.

In late July 2026, the European Commission published a guide with 67 practical examples. It is not legally binding, but it is considered an authoritative reference. It helps mainly with the question of what counts as commercial software, and it explicitly addresses small and medium-sized businesses as well.

Key Deadlines at a Glance

DateWhat applies
December 10, 2024The CRA enters into force
September 11, 2026Reporting duties for actively exploited vulnerabilities and severe security incidents
December 11, 2027Remaining obligations: risk assessment, technical documentation, conformity assessment, EU declaration of conformity and CE marking

The reporting duty works in three stages:

StageDeadline
Early warning24 hours
Detailed notification72 hours
Final report14 days for vulnerabilities, one month for incidents

In Germany, the BSI receives reports through CERT-Bund, and at EU level ENISA provides a single reporting platform. For micro and small enterprises, exceptions to the 24-hour deadline apply under certain conditions.

Who Is Affected

The rules address manufacturers, importers and distributors of products with digital elements that are made available on the EU market. For open source, it depends on how the software is marketed: freely available software is exempt as long as it is not distributed commercially. It counts as commercial, for example, if it is sold for a fee, if a paid enterprise version exists, or if it is monetized through forced data sharing. Voluntary donations, public funding or paid support for otherwise free software are considered non-commercial.

If you have software developed individually for a single client, you should assess the classification case by case, ideally before the contract is signed. Even without being directly affected, the topic can reach you: tenders, customer contracts and supply chain requirements may call for CRA evidence.

What to Prepare Now

December 2027 feels far away, but the reporting duty already applies. These steps are worth tackling first:

  1. Clarify your scope: Which products fall under the CRA, and what is your role in the supply chain?
  2. Define a reporting channel: Who reports, who decides, and who can be reached within 24 hours? The stages are in the deadline table.
  3. Create an SBOM: A software bill of materials lists all components, including open source dependencies and purchased parts. Incomplete documentation of purchased components is a typical problem area.
  4. Set up a vulnerability process: Define a support period, monitor vulnerabilities for at least five years and provide security patches.
  5. Anchor security by design and by default: Security belongs in the design and default configuration of new projects, not at the end.
  6. Pick a pilot product: Run through the requirements on one product before the whole portfolio follows.

What Happens in Case of Violations

Violations can lead to fines of up to 15 million euros or 2.5 percent of worldwide annual turnover. On top of that comes market access: from December 2027, CE marking including cybersecurity is a prerequisite for offering affected products in the EU.

Conclusion

The reporting duty is the first part of the CRA, and it already applies. If you build, sell or commission software, clarify your scope, your reporting channel and your software bill of materials now, and there will be enough time for the rest until December 2027. If you want to know what the CRA means for your software, get in touch. You can find more about our IT consulting.

Share

Frequently asked questions

  • The CRA is tied to products, not to company size. For micro and small enterprises, exceptions to the 24-hour reporting deadline apply under certain conditions, and the European Commission's guidance from July 2026 specifically addresses the needs of small and medium-sized businesses.

  • SBOM stands for software bill of materials. It lists every component of a piece of software, including open source libraries and purchased modules. When a vulnerability becomes known, it lets you quickly check whether your product is affected. It is considered the first step in CRA preparation.

  • Reporting channels for actively exploited vulnerabilities and severe security incidents have had to work since September 11, 2026. The remaining obligations, including risk assessment, technical documentation, conformity assessment and CE marking, apply from December 11, 2027.

Author of this article

JB

Juljan Blischke

Co-Founder & Engineering

Certified application developer. Has been building web applications, APIs and internal tools for years.

This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.