Chapter 2 of 8

2Device requirements

16 min read · 8 figures · 3 tables · 12 sources

A root of trust and a device identity cannot be added after shipment. The security functions of a connected device therefore have to be fixed before design freeze. The five acts translate into eight such device functions, and the Cyber Resilience Act (CRA) asks for all eight. All four example devices, from the battery tool to the logistics tracker, fall into the CRA default class and may assess their own conformity. Only a gateway sold on its own can become an important product as a router or firewall, and it then needs a notified body that does not yet exist under the CRA. The chapter introduces these four archetypes, derives the functions from the legal texts and shows where classification depends on a design choice.

2.1 Four device archetypes

We examine obligations, cost and architecture on four device archetypes. An archetype is a typical device that stands for a whole product group and brings that group’s usual combination of radio, path to the cloud and applicable acts. The four archetypes are a battery tool with BLE tracker, a machine with gateway, a building device under § 14a EnWG and a logistics tracker for assets, containers and trailers.

1. Battery tool with BLE tracker. A cordless drill, impact wrench, grinder or saw with a removable battery pack and a Bluetooth Low Energy (BLE) radio. The radio serves configuration and diagnostics through a smartphone app and lets the owner locate the tool. The app relays data to the manufacturer’s cloud. The tool is machinery within the meaning of the Machinery Regulation, a power-driven assembly with moving parts.168 The pack is a portable battery if it is sealed, weighs 5 kg or less and is not designed specifically for industrial use.169

2. Machine with gateway. A stationary machine (machine tool, packaging, process or handling machine) whose controller connects through an edge gateway to the operator’s network or a cloud service, via Ethernet, Wi-Fi or a cellular modem. The gateway may be built into the machine and placed on the market with it, or sold separately as a retrofit product. That distinction decides its CRA class.

3. Building device under § 14a EnWG. A heat pump, wallbox, air-conditioning unit or stationary storage battery that the distribution system operator may throttle under § 14a of the German Energy Industry Act.61 The Bundesnetzagentur’s determination BK6-22-300 of 27 November 2023 governs this grid-oriented control from 1 January 2024.74 A throttled device must still be able to draw at least 4.2 kW under direct control.74 The device receives a control signal and may report energy data. Some models also connect to an app via Wi-Fi or Ethernet.

4. Logistics tracker for assets, containers and trailers. A battery-powered, sealed device with satellite positioning (GNSS), a cellular radio (LTE-M, NB-IoT or 2G/4G) and often Bluetooth, mounted on equipment, containers or trailers. It reports location and sensor data such as temperature, shock or door state to a platform used by the fleet or asset owner. It is not machinery and carries a small portable battery.

2.2 Eight device functions

None of the five acts prescribes a component or uses the words “secure boot”. They describe outcomes that an engineering team has to translate into eight functions. The CRA asks for all eight, the Machinery Regulation for six (Figure 3).168, 171 Firmware integrity, authentication and the update mechanism shape the hardware. The SBOM, vulnerability handling and logging are processes as much as hardware. Data export and product identification concern data leaving the device.

Device functions by act
Figure 3: Device functions by act

Note: articles and annex points by act in Table 22. Sources: [141, 148, 168, 169, 170, 171].

Firmware integrity. The CRA requires products to protect stored, transmitted and processed data, commands, programs and configuration against unauthorised manipulation, to report on corruptions and to mitigate the effects of attacks.171 The Machinery Regulation requires that software and data critical for compliance with the safety requirements are “identified as such” and “adequately protected against accidental or intentional corruption”.168 Neither text prescribes a mechanism. The term secure boot appears only in Implementing Regulation 2025/2392, in the description of microcontrollers and microprocessors whose security functions protect “other products … such as secure boot chain”.149 The established engineering answer is a verified boot chain anchored in a hardware root of trust.

Update mechanism and support period. Vulnerabilities must be fixable through security updates, by default automatic, with an opt-out and the option to postpone.171 The manufacturer distributes updates securely, without delay and free of charge, and, where technically feasible, separately from functionality updates.171 The support period must reflect the time the product is expected to be in use and must be at least five years, unless the product is expected to be in use for less.171 Each security update must remain available for at least ten years after its release or for the rest of the support period, whichever is longer.171 The end date of the support period must be stated to the user.171 The maker of a machine that runs fifteen years therefore plans support for its expected use time, not for the minimum of five years.

Software bill of materials (SBOM). Manufacturers must draw up an SBOM “in a commonly used and machine-readable format covering at the very least the top-level dependencies”.171 The Commission may specify format and elements by implementing act.171 Until then, technical guideline TR-03183 Part 2 (version 2.1.0) of the German Federal Office for Information Security (BSI) gives formal and technical SBOM requirements, as non-binding guidance without a presumption of conformity.54 The Machinery Regulation adds its own inventory duty. The machine must identify the software necessary for safe operation and “be able to provide that information at all times in an easily accessible form”.168

Vulnerability handling and reporting. Only the CRA asks for this function. It requires remediation without delay, regular security tests, public disclosure of fixed vulnerabilities, a coordinated vulnerability disclosure policy and a contact address for reports.171 The user information must name a single point of contact.171 Since 11 September 2026, the reporting chain of Article 14 applies on top.171 BSI TR-03183 Part 3 covers the handling of incoming vulnerability reports, again as non-binding guidance.54

Authentication. Four of the five acts require authentication. The CRA demands a secure-by-default configuration and protection from unauthorised access.171 Under the RED, none of the three parts of EN 18031 confers a presumption of conformity “if, when applying its clauses 6.2.5.1 and 6.2.5.2, the user is allowed not to set and use any password”.148 A setup flow that lets the user skip the password is therefore outside the standard. The Data Act and the Machinery Regulation also presuppose protected access.168, 170

Data export interface. The Data Act requires access by design for all products placed on the market after 12 September 2026.170 Product data and related service data, including the metadata needed to interpret them, must be accessible to the user “by default, easily, securely, free of charge, in a comprehensive, structured, commonly used and machine-readable format, and, where relevant and technically feasible, directly”.170 Before the sale, the seller states the type, format and estimated volume of data, whether the product generates data continuously and in real time, where it stores data and how the user can access it.170 The data holder makes readily available data accessible when the user cannot access them directly on the device, where relevant and technically feasible “continuously and in real-time”.170 At the user’s request, it shares them with a third party.170 Typical implementations are a Bluetooth service, an OPC UA or Modbus endpoint or an authenticated cloud API, each with a data catalogue that matches the pre-contract information. Under the CRA the device has to secure the transfer.171 For batteries in its scope, the Batteries Regulation requires a passport that combines model data with data specific to the individual battery, including data “resulting from the use of that battery”.169 The path from device to passport backend becomes a compliance path when the battery management system is the only source of use data.

Logging. The CRA requires products to record and monitor relevant internal activity, including access to or modification of data, services or functions, with an opt-out for the user, and to report possible unauthorised access.171 The Machinery Regulation goes furthest. The machine “shall collect evidence of a legitimate or illegitimate intervention” in safety-relevant hardware, in the software and in its configuration.168 Its control system keeps a tracing log of intervention data and of the versions of safety software uploaded after placing on the market, “enabled for five years after such upload”, for use on reasoned request of a national authority.168 Control systems with self-evolving behaviour also keep data on safety-related decisions for one year.168

Product identification. The product or its software must be identifiable unambiguously under four of the five acts: the CRA in the user information,171 the Data Act in the pre-contract information,170 the Machinery Regulation for safety-relevant software168 and the Batteries Regulation with the QR code that every battery carries from 18 February 2027 and, for industrial batteries above 2 kWh, with the battery passport.169

2.3 A common security baseline

Four of the five acts ask for the same small set of device capabilities, and the CRA says so itself. Its essential requirements “include all the elements” of the RED cybersecurity requirements.171 By its own account, the CRA “could facilitate” compliance with the cybersecurity requirements of the Machinery Regulation, provided the manufacturer demonstrates the overlap through harmonised standards and a risk assessment that covers those risks.171 The Data Act, often read as the opposite of security, requires access “securely” and lets the data holder restrict sharing that could undermine the product’s security.170 Six capabilities make up this common baseline (Table 3).

Capability Meets requirements of Purpose
Hardware root of trust and verified boot CRA, RED, Machinery Regulation Protects firmware and safety software against tampering
Unique device identity, no shared default password CRA, RED, Data Act Needed for authenticated data export and for the RED standard EN 18031
Signed over-the-air updates with rollback protection CRA, Machinery Regulation Security updates for at least five years, each kept available for ten
Tamper-evident event log with software version history CRA, Machinery Regulation Machines must keep evidence of interventions and a five-year log of safety software
Authenticated, documented data export, local or cloud Data Act, CRA Uses the same identity and access model as the service channel
SBOM per firmware release, vulnerability intake, reporting runbook CRA Required since 11 Sep 2026, also for products already in the field
Table 3: Capabilities of the common security baseline

A product with a shared default password and unsigned firmware therefore fails four acts at once. Even a simple logistics tracker needs this baseline. Its user, typically the fleet operator, has a Data Act right to the position and sensor data.170 Trackers in the field are also exactly the installed base for which the CRA reporting duty already applies.171 A device without unique credentials, signed updates and an SBOM can neither be patched nor reported on within 24 hours.

2.4 Obligations by archetype

Every archetype falls under the CRA and the Data Act, and each has one obligation that is easy to miss (Table 4).170, 171 Several classifications depend on the design or on a reading the texts do not settle. In these cases the manufacturer has to document its classification explicitly.

Act and requirement Battery tool Machine Building device Logistics tracker
CRA: scope, reporting from 11 Sep 2026, full from 11 Dec 2027 Yes Yes, machine and gateway Yes Yes
CRA: class Default, the Bluetooth module does not raise the class Machine: default. Gateway sold on its own: conditional Class I (router) or Class II (firewall) Default, not a smart home security product Default, not a wearable
CRA: conformity route Module A Machine: Module A. Class I gateway: Module A only with harmonised standards applied in full, else B+C or H. Class II: B+C, H or EUCC Module A Module A
CRA: support period ≥ 5 years or expected use Expected use time of the machine, if longer than 5 years ≥ 5 years or expected use ≥ 5 years or expected use
RED (Reg. 2022/30), Art. 3(3)(d) Yes, also when connected via the app Conditional: gateway or controller with radio Conditional: models with Wi-Fi or cellular Yes
RED (Reg. 2022/30), Art. 3(3)(e) Yes if location or user data processed Conditional: personal data on the HMI or gateway Conditional: personal data, e.g. consumption profiles Yes: location data
Data Act, Art. 3(1) access by design Yes: usage, battery and location data Yes: machine operating data Yes: operating and energy data Yes: position and sensor data
Machinery Regulation, Annex III 1.1.9 / 1.2.1 Yes Yes, Annex I Part A only for ML-based safety functions Conditional: check the household-appliance exclusion No
Batteries Regulation: battery passport (Art. 77) No, as long as the pack is a portable battery Only if an industrial battery > 2 kWh is built in Storage > 2 kWh: yes No: portable battery
Batteries Regulation: QR code (Art. 13(6)) Yes If batteries are incorporated Yes, for the storage battery Yes
Batteries Regulation: end-user removable battery (Art. 11) Yes, packs are removable by design - - Yes, derogation only where needed for safety
Table 4: Requirements of the five acts by archetype

Note: our classification for the typical design, “Conditional” where the design or an open reading decides. Sources: [141, 149, 168, 169, 170, 171].

Battery tool. Three regimes meet in one housing. As machinery, the tool falls under the cybersecurity sections of the Machinery Regulation from 20 January 2027. The app channel must not create a hazard if it can change safety-relevant parameters such as speed, torque or kickback detection, and the safety firmware must be protected and identifiable.168 The BLE radio brings in the RED. A tool that reaches the internet only through the user’s phone is internet-connected radio equipment, because the text includes communication via other equipment.141 Location or user data add the privacy requirement.141 The built-in Bluetooth module is itself a Class I network interface, but it does not raise the tool’s CRA class.149, 171 Access by design under the Data Act covers usage, battery and location data.170 The pack gets a QR code, but no passport as long as it is a portable battery.169 A pack marketed only for professional or industrial use, by contrast, may count as an industrial battery. Its classification therefore has to be documented explicitly.

Machine with gateway. The machine itself stays in the CRA default class, because the core function of a machine tool falls into no category of important or critical products.171 The gateway is where classification becomes delicate. A gateway placed on the market on its own whose core function is to route traffic between the plant network and the internet matches the description of a router and is then a Class I product.149 A gateway sold only as an integral part of the machine is assessed with the machine, which stays default. The same hardware sold both ways needs two classifications. If the gateway is marketed with the core function of protecting the plant network by monitoring and restricting traffic, it fits the firewall description instead. It is Class II, with a mandatory notified body or certification.149 In our reading, a routing gateway that merely integrates firewall rules remains a router. For the installed base of long-lived machines, the Data Act’s Article 4 access right matters more than access by design, which only covers newly placed machines.170 The machine needs a notified body under the Machinery Regulation only if it embeds self-evolving, machine-learning safety functions.168

Building device. A heat pump or wallbox is not a smart home product with security functions that protect the physical security of consumers, so it stays in the CRA default class.149, 171 A home energy manager that routes between home network and internet may itself be a router. A smart meter gateway in the § 14a control path is a critical product.171 It belongs to the metering point operator, not to the device maker, and does not change the class of the device.171 The manufacturer also has to classify and document whether a domestic heat pump falls under the Machinery Regulation or under its household-appliance exclusion.168 A stationary storage battery above 5 kg counts as an industrial battery and needs a passport above 2 kWh.169 The battery passport therefore hits this archetype hardest.

Logistics tracker. The tracker is a default CRA product and internet-connected radio equipment that processes location data. Both RED points therefore apply, and with them EN 18031-1 and -2.141, 148 It is not a Class I wearable, because it is mounted on goods, not worn on the body.149 The Commission reads that class as products that collect health data.149 A badge that only reports position is outside it. A lone-worker badge with fall detection needs checking. The tracker remains a connected product under the Data Act, because it transmits data on behalf of its user, not of third parties.170 The least noticed obligation is in the Batteries Regulation. From 18 February 2027 a portable battery in a product must be “readily removable and replaceable by the end-user” with commercially available tools, and removal instructions must be published online.169 A potted, glued or welded tracker does not meet this. The exemption for devices used mainly around water applies only where it is needed for safety.169 An IP67 tracker on a trailer therefore qualifies only with that justification. Without it, the battery compartment must open with commercially available tools.

2.5 Conformity assessment routes

The CRA classifies a product by its core function, not by the components it contains. A product whose core function matches a category in Annex III is important (Class I or II), one matching Annex IV is critical, everything else is in the default class.171 Implementing Regulation 2025/2392 has described each category since 21 December 2025. It confirms that the product “as a whole” decides. A component with the core function of an important product does not by itself make the host product important.149 A product that can perform the functions of a category but whose core function is different is not in that category, just as a smartphone is not an operating system.149 Only the default class can always assess itself, the other classes only under conditions or not at all (Table 5).171

Class Relevant annex entries Conformity assessment
Default Everything not listed in Annex III or IV, including tools, machines, heat pumps, wallboxes and trackers Module A (internal control); B+C, H or a certification scheme voluntary
Important, Class I III-I.8 boot managers; III-I.10 physical and virtual network interfaces (incl. Bluetooth, Wi-Fi, Ethernet, fieldbus adapters); III-I.11 operating systems (incl. real-time OS); III-I.12 routers, modems intended for connection to the internet (incl. cellular modems), switches; III-I.14 microcontrollers with security-related functionalities; III-I.17 smart home products with security functionalities Module A only if harmonised standards, common specifications or a European certification scheme at level “substantial” are applied in full; otherwise B+C or H with a notified body
Important, Class II III-II.2 firewalls, intrusion detection and prevention systems; III-II.4 tamper-resistant microcontrollers (AVA_VAN 2 or 3) B+C, H, or a European certification scheme at level “substantial”
Critical IV.2 smart meter gateways and other devices for advanced security purposes; IV.3 smartcards and similar devices, including secure elements European certificate where a delegated act under Art. 8(1) requires it; otherwise the Class II routes
Table 5: CRA product classes and conformity assessment

Sources: [149, 171].

The components inside the four archetypes are full of important and critical products: the Bluetooth or cellular module, the real-time operating system and the microcontroller with secure boot in Class I, the secure element as a critical product. Their makers need their own conformity assessment for them. The tool, machine, heat pump and tracker nonetheless stay in the default class.149, 171 Buying CRA-compliant components therefore reduces the work but does not replace the manufacturer’s own assessment of the whole product.

The classification of a gateway is the most expensive. A Class I gateway cannot assess itself and needs a notified body as long as no CRA harmonised standard is cited in the Official Journal.171 No body is yet notified under the CRA.161 The Commission’s standardisation request M/606 schedules the standards for routers, modems and switches and for firewalls, including those specifically intended for industrial use, for 30 October 2026.147 Citation in the Official Journal follows only after that. BSI TR-03183 Part H describes how a manufacturer can use an ISO/IEC 27001-conformant management system for a Module H assessment.54 For a gateway launching in 2028, a notified body is therefore the planning case. A standard cited in the Official Journal by then would be an upside, not a basis for planning.

In summary

For most manufacturers, compliance is therefore an engineering task, not an approval process. Only selling a gateway on its own makes them depend on standards and notified bodies that are still missing. The next chapter shows what the eight functions cost per device and month.

Sources in this chapter12

Numbered as in the full reference list and the PDF.

  1. [54] Bundesamt für Sicherheit in der Informationstechnik. (2026). Technische Richtlinie BSI TR-03183: Cyber-Resilienz-Anforderungen an Hersteller und Produkte (Teil 1 v1.0.0, Teil 2 SBOM v2.1.0, Teil 3 v1.0.0, Teil H v1.1.0). https://www.bsi.bund.de/dok/TR-03183
  2. [61] Bundesministerium der Justiz. (2026). § 14a Energiewirtschaftsgesetz: Netzorientierte Steuerung von steuerbaren Netzanschlüssen und steuerbaren Verbrauchseinrichtungen. https://www.gesetze-im-internet.de/enwg_2005/__14a.html
  3. [74] Bundesnetzagentur. (2023). Festlegung BK6-22-300, Anlage 1: Netzorientierte Steuerung steuerbarer Verbrauchseinrichtungen. https://www.bundesnetzagentur.de/DE/Beschlusskammern/1_GZ/BK6-GZ/2022/BK6-22-300/Beschluss/BK6-22-300_Beschluss_Anlage1.pdf
  4. [141] European Commission. (2022). Commission Delegated Regulation (EU) 2022/30 supplementing Directive 2014/53/EU (RED) with regard to cybersecurity. https://eur-lex.europa.eu/eli/reg_del/2022/30/oj
  5. [147] European Commission. (2025). Annexes to the Commission Implementing Decision on a standardisation request to CEN, Cenelec and ETSI as regards products with digital elements in support of Regulation (EU) 2024/2847, C(2025) 618 final, 3 February 2025 (M/606). https://ec.europa.eu/transparency/documents-register/api/files/C(2025)618_1/de00000001069729
  6. [148] European Commission. (2025). Commission Implementing Decision (EU) 2025/138 amending Implementing Decision (EU) 2022/2191 as regards harmonised standards for cybersecurity of radio equipment. http://data.europa.eu/eli/dec_impl/2025/138/oj
  7. [149] European Commission. (2025). Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 on the technical description of the categories of important and critical products with digital elements pursuant to Regulation (EU) 2024/2847. https://eur-lex.europa.eu/eli/reg_impl/2025/2392/oj
  8. [161] European Commission. (2026). NANDO: Regulation (EU) 2024/2847 (Cyber Resilience Act), notifications and notifying authorities. https://webgate.ec.europa.eu/single-market-compliance-space/notified-bodies/notifying-authorities?filter=legislationId:167953
  9. [168] European Parliament and Council. (2023). Regulation (EU) 2023/1230 on machinery (Machinery Regulation). https://eur-lex.europa.eu/eli/reg/2023/1230/oj
  10. [169] European Parliament and Council. (2023). Regulation (EU) 2023/1542 concerning batteries and waste batteries (battery passport). https://eur-lex.europa.eu/eli/reg/2023/1542/oj
  11. [170] European Parliament and Council. (2023). Regulation (EU) 2023/2854 on harmonised rules on fair access to and use of data (Data Act). https://eur-lex.europa.eu/eli/reg/2023/2854/oj
  12. [171] European Parliament and Council. (2024). Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act). https://eur-lex.europa.eu/eli/reg/2024/2847/oj
Next

Contents

Report overview
  1. 1Deadlines and scope
  2. 2Device requirements
  3. 3Cost per device
  4. 4Technology and architecture
  5. 5Spotlight: logistics tracking
  6. 6Spotlight: Austria and Switzerland
  7. 7Vendor landscape
  8. 8Recommendations
  9. AMethod
  10. BLegal basis
  11. CCost model
  12. DVendor directory
  13. EFunding programmes
  14. About RUBINLAKE
  15. Disclaimer
  16. References