Cyber Resilience Act: Duties and Deadlines for Software — Security & GDPR article by Rui Codex

The EU Cyber Resilience Act (Regulation (EU) 2024/2847) requires software makers to build security into products, fix vulnerabilities for the product's support period and report actively exploited flaws to authorities. Reporting duties apply from 11 September 2026, and the main obligations apply from 11 December 2027.

Key takeaways

  • The Cyber Resilience Act applies to software placed on the EU market as a product, and it reaches companies outside the EU that sell there.
  • Manufacturers must handle vulnerabilities for the support period, which is at least five years unless the expected use time is shorter.
  • Reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026, while the full set of duties applies from 11 December 2027.
  • A software bill of materials is the practical starting point, because it shows whether a newly disclosed flaw affects your product.

Who has to comply with the Cyber Resilience Act?

Any company that places a product with digital elements on the EU market in the course of a commercial activity is generally a manufacturer under the Act. Standalone software counts as a product with digital elements, not only hardware that contains software.

The Act treats open-source software differently. Software developed outside a commercial activity is generally outside its scope, while open-source stewards carry a narrower set of duties. Whether your code falls on one side or the other depends on how it is developed and supplied, so check the text of the regulation in the official EUR-Lex version before you decide.

This article is general information and not legal or tax advice. Rui Codex offers technical implementation support, such as engineering a vulnerability-handling pipeline or generating software bills of materials, and does not provide legal, compliance or certification services.

What obligations does the Act place on manufacturers?

Manufacturers must design products for security, keep vulnerability handling running for the support period, document the product and carry out a conformity assessment before placing it on the market. These duties are set out in the text of Regulation (EU) 2024/2847, and the detail sits in its annexes.

Security by design and by default

The Act expects secure defaults, such as no shared default passwords, access control that is on from the start, and the ability to switch off features that are not needed. For a software vendor this means threat modelling and secure configuration are part of the release process, not a later hardening project.

Vulnerability handling and the SBOM

Manufacturers must identify and document vulnerabilities, including by drawing up a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies. Without that inventory, a team cannot tell within hours whether a newly disclosed flaw in a library reaches its product. The SBOM is only useful if it is generated from the build, not written by hand once a year.

Support period and documentation

Security updates must be provided for at least five years, unless the product's expected use time is shorter, as the official text of the regulation states. Technical documentation and the EU declaration of conformity must be kept and made available to market surveillance authorities. A support commitment you cannot staff is a liability, so align the promised period with your engineering capacity before you publish it.

Tip: Write the support period into the product documentation and the sales contract together. A mismatch between the two is an easy point of failure to miss during a review.

When do the obligations start to apply?

The Regulation entered into force on 10 December 2024, but its duties phase in. Reporting of actively exploited vulnerabilities and severe incidents applies from 11 September 2026, and the general application date is 11 December 2027, according to the official EUR-Lex text.

The gap between these dates is the practical window for most software companies. Reporting tooling, an SBOM pipeline and a vulnerability intake process take time to build and test, and they are hard to retrofit under pressure in the weeks before a deadline. The reporting duties have applied since 11 September 2026, so the intake and reporting process should already be running; plan the remaining work backwards from the general application date, 11 December 2027.

How does vulnerability reporting work in practice?

Manufacturers report an actively exploited vulnerability in stages: an early warning, a notification with more detail, and a final report after a fix is available. The timings are set in the regulation, including an early warning within 24 hours of becoming aware, as described in the text on EUR-Lex.

The reporting channel is designed around the national CSIRT and ENISA, and the European Union Agency for Cybersecurity, ENISA, coordinates the single reporting platform described in the Act. Your process must therefore decide early who in your organisation can classify a flaw, who signs off a report, and how you reach the correct authority.

Each stage has a failure mode. An early warning sent before anyone has confirmed exploitation can overstate the problem, while a late notification because the team waited for a perfect analysis breaks the timeline. A written triage rule, with named owners, avoids both.

Hypothetical examples of applying the Act

Here are two hypothetical scenarios:

Scenario A. A company sells a desktop application that bundles a third-party compression library. A public advisory reports active exploitation of that library. Because the team generated an SBOM at each build, it finds the affected version in minutes, decides whether the flaw is reachable in its product, and prepares a fixed release. Without the SBOM, the same search would depend on memory and manual review of old builds.

Scenario B. A second company licenses an on-premises analytics product and promises longer security support than the minimum. Its sales team agrees to the longer period in a contract, but the engineering team has not budgeted for backporting patches to older versions. When the first support request arrives, the company must either fund the work or breach its own commitment. The lesson is that the support period is an engineering decision, not only a commercial one.

What should a software company prepare first?

Start with an inventory of what you ship, then add the processes that reporting depends on. Work in this order, because each step makes the next one cheaper.

  • List every product you place on the EU market, including versions still in support.
  • Generate an SBOM from the build pipeline for each release, covering at least top-level dependencies.
  • Name an owner for vulnerability intake and a second person who can classify and sign off a report.
  • Define the support period per product and record it in both documentation and contracts.
  • Test the reporting steps with a tabletop exercise, because the reporting duties already apply.

Technical teams usually need help with the pipeline and the intake process rather than the legal reading. Rui Codex offers custom software engineering and system integration work that can connect build tooling to an SBOM store and a ticketing workflow. For a broader view of security topics, see the security and compliance engineering articles on the Rui Codex blog.

Where does the Act leave questions open?

Some details depend on implementing acts, harmonised standards and guidance that are still being developed, so the position can change before the general application date of 11 December 2027. Treat the official text as the source of truth and review your plan when new implementing material is published.

Where the text is open, document your interpretation and the reasons for it. A written record of a reasonable reading is more useful during an audit than an assumption that nobody can explain later. Architecture choices such as modular updates and a clear dependency policy, described in the Rui Codex technology overview, make it easier to change course when the rules become clearer.

Frequently Asked Questions

Does the Cyber Resilience Act apply to software sold only as a service?

The Act covers products with digital elements, so software supplied as a product in the EU market is in scope. A hosted service that is not supplied as a product is generally outside it, but remote data processing linked to a product is treated differently. Check the boundary against the official text for your specific offering.

When must manufacturers start reporting actively exploited vulnerabilities?

Reporting obligations for actively exploited vulnerabilities and severe incidents apply from 11 September 2026. Manufacturers send an early warning first, followed by a notification and a final report. Your reporting process should already be in place and tested, not improvised when the first report is due.

What is an SBOM and is it required?

A software bill of materials is a machine-readable inventory of the components in a product. The Act requires manufacturers to draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. It is the practical basis for judging whether a newly disclosed flaw affects your product.

How long must security updates be provided?

Security updates must be provided for at least five years, unless the product's expected use time is shorter. The support period should be documented in the product information and in customer contracts. A longer commitment is a business decision, but it must be backed by engineering capacity.

Can a company outsource Cyber Resilience Act compliance to a developer?

Manufacturers remain responsible for compliance even when external engineers build parts of the product. Outside developers can provide technical implementation support, such as building a vulnerability pipeline, but the manufacturer keeps responsibility for the declaration of conformity. Legal review should come from qualified counsel.

Sources

Conclusion

The Cyber Resilience Act turns security and vulnerability handling into ongoing product obligations, with reporting from 11 September 2026 and full application from 11 December 2027. The companies that cope best will be the ones that treat the SBOM, the support period and the reporting process as engineering work with named owners, rather than as paperwork to finish at the last minute. Start with an inventory of your products and a tested intake process. If you want technical help building the pipeline, email info@ruicodex.com to discuss your project, or request a project consultation.

Tags: Cyber Resilience Act software vendors SBOM vulnerability handling EU regulation product security software compliance GDPR compliant software

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request