NIS2 vs CRA: what each EU security law means for Android device makers

A circuit board inside the ring of EU stars, for the Cyber Resilience Act and NIS2

When we talk with device makers about the EU Cyber Resilience Act (CRA), the NIS2 Directive often comes up in the same breath. Both are EU cybersecurity laws and both have 24-hour reporting deadlines, so they're easy to mix up.

They regulate different things. NIS2 sets rules for organizations that run important services, and the CRA sets rules for products with digital elements, which covers almost every Android device sold in the EU. As a device maker, you can fall under both.

NIS2 sets rules for organizations, the CRA for products

NIS2 (Directive (EU) 2022/2555) is a directive. Each EU country turns it into its own national law, and the deadline for that was 17 October 2024. It covers medium-sized and large organizations in 18 sectors, such as energy, transport, health, digital infrastructure and the manufacture of critical products. They have to manage their cybersecurity risks, including the risks in their supply chain, and report significant incidents.

The CRA (Regulation (EU) 2024/2847) is a regulation, so the same text applies directly in every EU country. Its rules cover hardware and software products with digital elements and the companies that make, import or sell them. The CRA became law on 10 December 2024. Its reporting obligations have applied since 11 September 2026, and from 11 December 2027 the rest of the CRA applies too.

  NIS2 CRA
Regulates Organizations in 18 sectors Products with digital elements
Type of law Directive, a national law in each EU country Regulation, the same text in every EU country
Dates National laws due by 17 October 2024 Reporting since 11 September 2026, everything else from 11 December 2027
Main duties Risk management, supply chain security, incident reporting Secure design, vulnerability handling, security updates, CE marking
Reports go to The national CSIRT or authority The national CSIRT and ENISA, through one platform
Fines up to 10 million euros or 2% of worldwide annual turnover* 15 million euros or 2.5% of worldwide annual turnover

* For essential entities. For important entities, up to 7 million euros or 1.4%. In each case, the higher amount counts.

As a device maker, you can fall under both laws

The CRA covers almost every device you sell in the EU. If it runs software and connects to a network or to another device, it's a product with digital elements. Only a few product groups are left out because their own laws already cover them, such as medical devices, cars and aircraft.

NIS2 can apply to your company directly. The manufacture of computer, electronic and optical products is one of its sectors. If you make devices and have at least 50 employees, or more than 10 million euros in both annual turnover and balance sheet total, check your country's NIS2 law. You may have to meet its requirements for your own organization, from risk management to incident reporting.

NIS2 also reaches you through your customers. Larger hospitals, utilities and logistics companies fall under NIS2 and have to manage the security of their suppliers. They pass that on in tenders and contracts: how long you ship security updates, whether you deliver an SBOM (the parts list of your software), and how you handle vulnerabilities. Our advice: answer these questions the way the CRA asks you to. It's the same work, and you only want to do it once.

Both laws set 24-hour deadlines, triggered by different events

Under NIS2, you report significant incidents: events that seriously disrupt your services or cause considerable damage to you or others. An early warning goes to your national CSIRT (the computer security incident response team) or authority within 24 hours. A notification follows within 72 hours and a final report within a month.

Under the CRA, you report actively exploited vulnerabilities in your product and severe incidents that affect its security. The deadlines are 24 and 72 hours as well. The final report is due 14 days after a fix is available for a vulnerability, or one month after the notification for an incident. One submission through ENISA's Single Reporting Platform reaches both your national CSIRT and ENISA, the EU's cybersecurity agency. We cover the details in CRA reporting: what Android device makers need today.

One attack can trigger both. Say attackers exploit a vulnerability in your devices' OS and use it to get into your update server. The exploited vulnerability needs a CRA report. If your company falls under NIS2 and the attack disrupts your update service, that can need a NIS2 report too.

An OS doesn't make your device an important product

The CRA sorts products into three groups. The group decides how you show that your device meets the CRA's requirements before you put the CE marking on it:

  • Default products: most products belong here, such as smart speakers, mobile apps and computer games. You can assess conformity yourself.
  • Important products (Annex III, Class I and II): for example operating systems, routers, firewalls and smart home security devices like door locks. Depending on the class and the standards you apply, an independent testing organization (a notified body) may have to check your device.
  • Critical products (Annex IV): smart cards, secure elements and smart meter gateways. A notified body is always required.

Operating systems are on the Class I list, and it's easy to read that as covering every Android device. What counts is your device's core functionality. A kiosk, a POS terminal or an HMI panel runs Android underneath, but its core functionality is that of a kiosk, a POS terminal or an HMI panel. In our reading, most of these devices are default products. If your device's main job is on the Annex III or IV lists, like a router or a smart door lock, the stricter rules apply.

For the OS, both laws need the same work

For your devices, both laws lead to the same tasks on the OS level: know what runs on your devices, watch for vulnerabilities, build and ship fixes fast, and keep doing it for years. The CRA spells this out: an SBOM for every release, a support period of, as a rule, at least five years, and protection of the software's integrity. On Android, that's verified boot and signed OTA updates.

We build and maintain custom Android OS for device makers and automate as much of that work as we can. Automated OS pipelines in the Emteria Hub build your images, create an SBOM for every release and sign everything with your own keys. Fixes reach your fleet as OTA updates. Each major Android version gets at least five years of security updates from its release, included in the contract. Our CRA support covers this OS work. It helps you meet your CRA obligations, and it gives you solid answers when a customer asks about your supply chain under NIS2. The obligations themselves stay with you as the manufacturer.

If you sell Android devices in the EU and aren't sure where you stand, talk to us. Tell us about your device and the Android version it runs, and we'll show you what both laws mean for its OS.

This post is an overview from the OS perspective, not legal advice. We rewrote it in November 2026 to match the final texts of both laws.

Sources:

Build unique products, boost device performance

See why Emteria is the chosen Android™ customization & management platform for OEM solution builders, and what it can do for your team and customers.

Book live demo
Android-head-use-cases
Back to Blog

Table of contents

emteria Demo
See emteria in action