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.