Simplify Data Logo
  • Services
      • App Development
      • Web Development
          • Wordpress Development
          • Wordpress Support
          • Accessibility
      • Software Development
      • IT Consulting SME
          • Legacy modernisation
      • Business Analytics
          • Power BI
          • Metabase
      • Artificial Intelligence
      • SEO & AI visibility
      • Maintenance & Support
  • Managed Services
      • Zero-Trust Networking VPN
      • Managed email & groupware
  • Products
      • QRFlow
      • WooCommerce Interface
      • Open Source Projects
  • About us
      • Career
  • Blog
  • Contact
Software Development

Cyber Resilience Act 2027: what software and app firms need to prepare

Simplify Data Team
November 16, 2026
5 Min. Read
Cyber Resilience Act 2027: what software and app firms need to prepare
Simplify Data
Simplify Data GmbH
www.simplify-data.de
Cyber Resilience Act 2027: what software and app firms need to prepare

Simplify Data Team • November 16, 2026 • 5 min Lesezeit

Anyone placing software or apps on the EU market generally falls under Regulation (EU) 2024/2847, the Cyber Resilience Act (CRA). Two dates matter: reporting obligations for actively exploited vulnerabilities and severe incidents have applied since 11 September 2026. The main requirements for products and manufacturers apply from 11 December 2027. For software houses and app agencies, the CRA is therefore no side issue (as of November 2026).

Please note: this article is not legal advice. Whether a specific product falls under the CRA depends on its classification as a "product with digital elements" and on the exemptions.

What the CRA regulates

The CRA sets EU-wide cybersecurity requirements for products with digital elements. These are hardware and software whose intended or foreseeable use includes a data connection to a device or network. That covers connected devices as well as pure software such as mobile apps, desktop programs or firmware.

Who is affected

The obligations fall mainly on manufacturers: anyone who develops a product, or has it developed, and places it on the market under their own name or brand is a manufacturer. Importers and distributors have obligations too. An agency that builds an app for a client and publishes it under the client's name is usually not the manufacturer itself. A company that offers its own products, such as an industry app under its own brand, can be.

What is not covered, or only partly

  • Pure online services with no product link (classic SaaS) are not directly covered by the CRA. NIS2 is more likely to apply. If the cloud part belongs to an app or device and is needed for it, it may still count.
  • Non-commercial open-source software is exempt. If a company offers the same software as part of a business activity, the picture can change.
  • Open-source stewards that support projects on a sustained basis are subject to a lighter regime.

The timeline

Date What applies
10 December 2024 The CRA enters into force
11 September 2026 Reporting obligations for actively exploited vulnerabilities and severe incidents
11 December 2027 Full application: essential requirements, conformity assessment, CE marking

Reports go through a single European reporting platform to the competent CSIRT and ENISA. The process has stages: an early warning within 24 hours, a notification with an initial assessment within 72 hours, and a final report. For vulnerabilities the report is due no later than 14 days after a corrective measure becomes available, for incidents no later than one month after the notification.

What you need before placing a product on the market

Manufacturers must demonstrate security across the whole lifecycle. This includes:

  1. Risk assessment: a cybersecurity risk assessment covering planning, development, delivery and maintenance.
  2. Technical documentation: how the requirements in Annex I were implemented.
  3. Conformity assessment: a self-assessment for most products, an external body for particularly critical product classes.
  4. EU declaration of conformity and CE marking.
  5. User information: a contact point for vulnerabilities, guidance on secure use and the end date of the support period.
  6. Vulnerability management: document and fix vulnerabilities and provide security updates.

The support period is, as a rule, at least five years unless the product is clearly expected to be used for a shorter time. Security updates must be provided during that period.

What changes in day-to-day development

The CRA does not prescribe a specific framework, but it does require traceable security in a development team's daily work.

Dependencies and SBOM

Manufacturers must know the components of their product. The CRA requires a software bill of materials (SBOM) in a commonly used, machine-readable format that covers at least the top-level dependencies. In practice: maintain lockfiles, generate an SBOM in the build (for example in CycloneDX or SPDX format) and check automatically for known vulnerabilities.

Updates and vulnerability process

  • An update path must be planned from the start, for apps including store review and a minimum version.
  • You need a documented process: receive a report, assess, fix, inform.
  • Secure defaults: no default passwords, access control, protection of data at rest and in transit.
  • Secrets do not belong in the repository, and logging should capture security-relevant events.

Custom software for clients

For software that a client orders individually and runs itself, the manufacturer role is not always clear. Delivery, branding and who is responsible for updates are decisive. Record this in the contract and, if in doubt, get legal advice rather than ignoring the CRA.

Penalties

Breaches of the essential requirements can be fined up to EUR 15 million or 2.5 percent of worldwide annual turnover. Relief is foreseen for micro and small enterprises, for example for technical documentation and advisory support.

Checklist for 2026 and 2027

  1. Build a product list: which apps, libraries and devices do you release under your own brand?
  2. Check whether open-source components are used commercially.
  3. Define a reporting route for actively exploited vulnerabilities and incidents, since the duty already applies.
  4. Generate an SBOM in the build process and scan dependencies continuously.
  5. Set a support period per product and communicate it to users.
  6. Put the update mechanism and vulnerability process into your project template.
  7. Review client contracts: who is the manufacturer, who is responsible for updates?
  8. Start the technical documentation early, not shortly before December 2027.

How Simplify Data can help

We build custom software and apps so that update paths, dependencies and operations can be documented. That is the technical basis for the CRA requirements. We do not replace the legal assessment of the manufacturer role. More about our services: software development and app development. For questions about your product: get in touch.

Sources

  • EUR-Lex: Regulation (EU) 2024/2847 (Cyber Resilience Act)
  • European Commission: Cyber Resilience Act

This article is for general information only and is not legal advice; for your specific case, please consult a lawyer.

© 2026 Simplify Data GmbH www.simplify-data.de
Back to Blog

Table of Contents

  • 1.What the CRA regulates
  • –Who is affected
  • –What is not covered, or only partly
  • 2.The timeline
  • 3.What you need before placing a product on the market
  • 4.What changes in day-to-day development
  • –Dependencies and SBOM
  • –Updates and vulnerability process
  • –Custom software for clients
  • 5.Penalties
  • 6.Checklist for 2026 and 2027
  • 7.How Simplify Data can help
  • 8.Sources

Actions

Our services
  • App Development
  • Web Development
  • Software Development
  • IT Consulting SME
  • Business Analytics
  • Artificial Intelligence
  • SEO & AI visibility
  • Maintenance & Support
  • IT services Kiel & Hamburg
Service & Legal
  • Legal notice
  • Privacy policy
Contact
  • Simplify Data GmbH
  • Königsweg 48, 24114 Kiel
  • Phone: 0431 705 770 24
  • Email: info@simplify-data.de

Copyright © 2026 Simplify Data GmbH