app-entwickeln-lassen.de LogoApp entwickeln lassen

Legal, Privacy & Security

NIS2 and the Cyber Resilience Act: What Applies to Software and Apps?

app-entwickeln-lassen.de editorial team 6 min read
Contents
  1. NIS2 vs. CRA at a glance
  2. NIS2: who is covered and what is required
  3. Cyber Resilience Act: obligations for software manufacturers
  4. Which apps are actually affected?
  5. Preparation: what to do now
  6. Conclusion
  7. Frequently Asked Questions

NIS2 and the Cyber Resilience Act (CRA) are the EU's two central cybersecurity frameworks – and both affect software and apps, though in different ways. NIS2 obliges organisations in certain sectors to implement security measures and report incidents, while the CRA sets requirements for products with digital elements, including software you place on the market. This article explains what applies when and which steps you should take now.

NIS2 vs. CRA at a glance

The two frameworks are often mentioned together, but they take different approaches:

AspectNIS2Cyber Resilience Act
Legal formEU directive, transposed into national law (in Germany mainly via the BSI Act)EU regulation, directly applicable
Who it addressesEntities (companies, public bodies) in specific sectorsManufacturers, importers and distributors of products with digital elements
SubjectSecurity of the entity's own operations and servicesSecurity of the product across its lifecycle
Core dutiesRisk management, reporting significant incidents, management accountabilitySecurity by design, vulnerability handling, security updates, conformity assessment, CE marking
TimelineEU transposition deadline was October 2024; Germany transposed the directive in late 2025 after delaysIn force since December 2024, reporting duties from September 2026, full application from December 2027

NIS2: who is covered and what is required

NIS2 covers far more organisations than its predecessor. It applies to entities in sectors such as energy, transport, health, finance, digital infrastructure, waste management, food, manufacturing and digital services – generally from medium size upwards. For some areas, such as certain digital infrastructure providers, size is not a threshold. Check whether your organisation is in scope using the national rules and the tools published by your national cybersecurity authority (in Germany, the BSI).

Entities in scope must, among other things:

  • implement appropriate technical and organisational risk-management measures covering access control, encryption, backups, business continuity and vulnerability handling,
  • address supply-chain security – including the software and service providers they rely on,
  • report significant incidents in stages: an early warning within 24 hours, an incident notification within 72 hours and a final report within one month,
  • register with the competent authority,
  • hold management accountable – executives must approve and oversee the measures and undergo training.

What this means for app projects: Even if your company is not in scope itself, your customers may be. They will ask for security evidence, update commitments and reporting channels – and pass the requirements on to software suppliers through contracts.

Cyber Resilience Act: obligations for software manufacturers

The CRA applies to "products with digital elements" made available on the EU market. That includes connected hardware as well as standalone software – so in principle apps, desktop programs and firmware. Pure software-as-a-service is largely out of scope unless it is a remote data processing solution belonging to a product, such as the backend of a smart-home app. Open-source software supplied outside a commercial activity is exempt, and certain sectors such as medical devices have their own rules.

Manufacturers must, among other things:

  1. Build in security from the start: risk assessment, secure defaults, protection of data and interfaces, minimal attack surface.
  2. Handle vulnerabilities: maintain a software bill of materials (SBOM), fix vulnerabilities promptly, provide a contact point for security reports and a coordinated disclosure policy.
  3. Deliver security updates for a defined support period reflecting the expected use time – generally at least five years unless the product is expected to be used for less.
  4. Report actively exploited vulnerabilities and severe incidents, also within short, staged deadlines. These reporting duties have applied since September 2026.
  5. Demonstrate conformity: technical documentation, conformity assessment and CE marking. For most products a self-assessment is sufficient; categories classed as "important" or "critical" face stricter procedures.

Which apps are actually affected?

The boundaries are complex in detail, but a few rules of thumb help:

  • App for a connected device (IoT, smart home, wearable, machine): very likely relevant under the CRA, often together with the device and its cloud backend. More in IoT and Bluetooth apps.
  • Commercially distributed standalone app, e.g. via the app stores: in principle a product with digital elements.
  • Internal app used only within your own company and not placed on the market: generally not covered by the CRA, but it may fall under the operator's NIS2 duties.
  • Custom development for a client: who counts as the manufacturer depends on who places the product on the market under their own name – often the client. Clarify roles and duties in the contract.

Preparation: what to do now

  1. Check applicability: Is your organisation covered by NIS2? Which of your products are products with digital elements under the CRA?
  2. Set up a reporting process: Who detects, assesses and reports incidents and exploited vulnerabilities – including at weekends?
  3. Integrate SBOM generation and dependency management into your build pipeline, including automated vulnerability scans.
  4. Define the support period and reflect it in budgets and maintenance contracts; see app maintenance costs for guidance on calculation.
  5. Embed security testing: secure development following OWASP, regular penetration tests before releases with major changes.
  6. Build documentation continuously: risk assessments, architecture, test reports and update history – not just before an audit.

If you are planning a new app, these requirements can be built in cost-effectively from the start. With us, secure architecture, GDPR-compliant hosting and maintained dependencies are part of the fixed-price offer we prepare after a free analysis – request one via the offer wizard.

Note: This article is not legal advice. The scope, deadlines and exemptions of NIS2 and the CRA are complex and are being refined further through guidance and standards. Have your specific case reviewed by experts.

Agentic coding workshop for your team? From €799 net – request a quote by e-mail

Conclusion

NIS2 governs the security of organisations, the CRA the security of products – software vendors are often affected by both, directly or through their customers' requirements. The first CRA reporting duties have applied since September 2026, and the remaining requirements apply in full from December 2027. Building vulnerability management, SBOMs, update commitments and reporting processes now lets you comply with reasonable effort and makes your apps measurably more secure along the way.

Frequently Asked Questions

Does the Cyber Resilience Act apply to apps?

In principle yes, if an app is made available on the EU market as a product with digital elements. Pure SaaS offerings are largely exempt, while apps for connected devices and commercially distributed apps are generally covered.

When do the CRA obligations apply?

The regulation has been in force since December 2024. Reporting duties for actively exploited vulnerabilities and severe incidents have applied since September 2026, and the remaining requirements apply from December 2027.

My company is not covered by NIS2 – do I still need to act?

Often yes, because customers covered by NIS2 must secure their supply chain and pass requirements on to their software suppliers. The CRA may also apply to your products independently of NIS2.

What is an SBOM?

A software bill of materials is a machine-readable list of all components and dependencies of a piece of software. It lets you quickly determine whether a product is affected when a new vulnerability becomes known.

This article was written by the editorial team of app-entwickeln-lassen.de – the app and AI development service of jocapps GmbH, based in Freiburg, Germany, and building apps since 2014. The content is for general information and does not replace individual (legal) advice.

You might also like

Legal, Privacy & SecurityCopyright of AI-Generated Code: Who Owns What?

Copyright of AI-generated code explained: when code is protected, what tool terms and open-source licences mean, and how to secure your rights by contract.

7 min read
Legal, Privacy & SecurityData Processing Agreements (DPA) for App Development and Hosting

DPAs for app development and hosting: when you need a data processing agreement, what it must contain and how to review providers and sub-processors properly.

6 min read
Legal, Privacy & SecurityEU Data Residency for Apps: Server Location and International Transfers

EU data residency for apps: what server location achieves, when an international transfer occurs and how to integrate cloud, analytics and AI services safely.

6 min read
Legal, Privacy & SecurityTracking Consent in Apps: What Germany's TDDDG Requires

Tracking consent in apps under Germany's TDDDG: when you need consent, what a compliant consent dialogue looks like and how to start SDKs correctly.

6 min read
Legal, Privacy & SecurityLiability for App Defects: What Clients Need to Know

Liability for app defects under German law: when the agency is liable, what rights clients have after acceptance and how to set up contracts and maintenance.

7 min read
Legal, Privacy & SecurityLegal Notice, Privacy Policy and Terms in Your App: A Guide

Legal notice (Impressum), privacy policy and terms in your app: which disclosures German law requires, where they belong and how to integrate them cleanly.

6 min read