Contents
RegulationEU

EU Cyber Resilience Act

Horizontal cybersecurity requirements for products with digital elements

The EU Cyber Resilience Act sets cybersecurity duties for products with digital elements placed on the Union market; type-approved vehicles are excluded, while many aftermarket devices and some supplier products are still covered.

What it is

The EU Cyber Resilience Act is the Union’s horizontal regulation on cybersecurity for products with digital elements. It covers hardware and software placed on the Union market, including components sold on their own and remote data-processing solutions supplied with the product. Manufacturers design these products securely, provide security updates, and document that work. On an automotive programme the Act applies to a digital product sold in its own right. The type-approved vehicle, and the systems covered with that approval, follow the vehicle type-approval route.

Who it applies to

The manufacturer who places an in-scope product on the EU market holds the main obligations: risk-based design, technical documentation, conformity assessment, vulnerability handling, and security updates. Importers and distributors must make sure they supply products for which those duties have been met. Inside a vehicle company the split follows the product being placed on the market. Type-approved vehicles are outside the Act, together with systems and components covered by that approval. Aftermarket devices and some supplier products are not excluded. A fleet tracker sold to operators, a workshop diagnostic interface, a consumer dongle, or a software package licensed on its own can fall under the Act while the car it attaches to does not.

What it covers

For an in-scope product the Act requires security to be designed in and enabled by default, on the basis of a cybersecurity risk assessment. The manufacturer maintains a vulnerability-handling process, provides security updates through the support period, and gives users clear information on the product’s security properties and on how to report a weakness. Technical documentation describes the product, the risks, and the support arrangements; for software this includes a bill of materials of the components used. Reporting of actively exploited vulnerabilities and severe incidents applies since 11 Sep 2026. Full obligations, including conformity assessment and CE marking, apply from 11 Dec 2027. Ordinary products are assessed by the manufacturer. Important and critical product categories face a stricter assessment.

Duty What it means on a programme
Secure design Risk assessment, secure defaults, and documented controls before sale
Vulnerability handling Intake, analysis, fixes, and coordinated disclosure
Security updates Updates available through the stated support period
User information Security properties and a way for users to report weaknesses
Market placement Technical documentation, conformity assessment, and CE marking

How it fits with other documents

Type-approved vehicle cybersecurity continues to rest on UN Regulation No. 155, which requires a cybersecurity management system, and on the software-update requirements of UN Regulation No. 156. Teams usually implement that work with ISO/SAE 21434, which describes an engineering lifecycle for vehicle cybersecurity. Those documents remain the reference for the excluded vehicle and its approved systems. A product the Act still regulates needs its own conformity file.

ISO 26262 remains the reference for functional safety of E/E systems. The Act is a market-access regulation for cybersecurity of products with digital elements. Where one electronic control unit is sold both as a type-approved component and as a standalone product, the two sales paths can sit under different rules. A wireless aftermarket device can also have to satisfy radio-equipment requirements in parallel with this Act.

In practice

Record a scope decision for every item you place on the EU market. Include the vehicle, approved components, aftermarket hardware, diagnostic and workshop tools, and standalone software. For each in-scope item, name who receives vulnerability reports, who decides a fix, and how a security update reaches the devices already sold. Tools and dongles are easy to overlook because they are absent from the vehicle bill of materials. In supplier contracts, state who is the manufacturer for this Act, who keeps the technical documentation, and how reports are passed between the supplier and the brand. Processes already used for UN Regulation No. 155, such as risk assessment, update testing, and incident triage, can be reused where the technical work is the same. Keep a separate legal scope so the vehicle approval evidence and the evidence for a product this Act covers stay in their own files.

What it means for your discipline

  • CybersecurityCore

    You own market-access cybersecurity for every in-scope product: the risk assessment, vulnerability handling, incident reporting, and the conformity evidence. Keep that file separate from the vehicle type-approval cybersecurity case.

  • HPC & application softwareCore

    Software sold on its own, and software inside an in-scope device, must be maintained so vulnerabilities are fixed during the support period. The technical documentation includes a software bill of materials and a described update path.

  • Software update & OTACore

    Security updates throughout the support period are a duty of the manufacturer, including for tools and aftermarket units that never pass vehicle type approval. You need a way to build, deliver, and record each update for products already in the field.

  • E/E architecturePartial

    The architecture split between the type-approved vehicle and products sold separately decides which rule applies. Record that boundary per box, tool, and software product before design evidence is written.

  • Hardware & siliconPartial

    Hardware is in scope when the product itself is in scope, including aftermarket units and supplier hardware placed on the market on its own. Secure defaults, protected debug access, and a realistic support period belong in the technical file.

  • Base softwarePartial

    Basic software in a type-approved controller follows the vehicle rules. When the same stack ships in an aftermarket or standalone product, its secure configuration and update services become part of that product's evidence under this Act.

  • Diagnostics & lifecyclePartial

    Workshop interfaces, diagnostic dongles, and PC diagnostic applications can be products with digital elements even though they are absent from the vehicle. They need vulnerability handling and security updates of their own.

  • Functional safetyPartial

    Functional safety stays on its own standard and approval path. Where an in-scope product can affect a safety-related function, the cybersecurity risk assessment still has to cover that influence and remain distinct from the vehicle safety case.

No direct stake: Networks & communication