EU Cyber Resilience Act Guide for Automotive OEMs & Tier-1 Suppliers
Excluded for vehicles and for components designed exclusively for them. In-scope products are default class unless their core functionality matches an Annex III or Annex IV category.
The Cyber Resilience Act does not apply to vehicles under Regulation (EU) 2019/2144 or to components designed and constructed exclusively for integration into those vehicles (Article 2(2)(c)). A generic equivalent sold through channels open to the general public is in scope, whatever the stated intended use. For in-scope products, Article 14 reporting applies from 11 September 2026 and the other obligations apply from 11 December 2027. Annex III has no automotive category, so an in-scope product is default class unless its core functionality matches a listed category.
Last updated 26 October 2026
Does the CRA apply to vehicles and vehicle components?
The CRA does not apply to vehicles under Regulation (EU) 2019/2144 or to components designed and constructed exclusively for integration into those vehicles. Article 2(2)(c) excludes products with digital elements to which Regulation (EU) 2019/2144 applies. That Regulation covers vehicles of categories M, N and O and the systems, components and separate technical units designed and constructed for them. Delegated Regulation (EU) 2025/1535 adds the same exclusion for L-category vehicles under Regulation (EU) No 168/2013.
Commission guidance C(2026) 5252, points 244 to 246, gives the test for components. A component designed and constructed exclusively for integration into those vehicles is outside the CRA. The exclusion applies to sales to the vehicle manufacturer and to sales to other operators in the automotive supply chain. An electronic control unit (ECU), a telematics control unit (TCU), a gateway, an infotainment head unit or a V2X on-board unit built only for those vehicles is therefore excluded.
Two cases bring a product into scope. A generic component that can go into different types of products is in scope. A generic equivalent offered through channels open to the general public, such as retail or open online sales, is in scope whatever the stated intended use. Sales only through restricted business-to-business channels in the automotive supply chain can show exclusive design and construction.
Which CRA class applies to an in-scope automotive product?
Classification follows the core functionality of the product (Article 7(1)). Annex III has no category for vehicle safety functions, for in-vehicle networks or for automotive products in general. An in-scope automotive product is therefore default class unless its core functionality matches a listed category.
Implementing Regulation (EU) 2025/2392 gives the technical description of each Annex III and Annex IV category. Categories that can apply to automotive suppliers include routers and modems intended for the connection to the internet (Class I point 12), operating systems (Class I point 11) and microcontrollers with security-related functionalities (Class I point 14). Tamper-resistant microcontrollers are Class II.
The integration of an important component does not make the larger product important. A telematics unit that contains a cellular modem keeps the class of its own core functionality. Record the classification decision in the technical documentation for each product, and review it when the core functionality changes.
Key Technical Security Obligations Under Annex I
Annex I Part I sets the essential cybersecurity requirements that an in-scope product must meet before it gets the CE marking. The requirements apply on the basis of the Article 13(2) risk assessment. The requirements below apply directly to connected automotive hardware.
- Secure by default. The product is made available with a secure by default configuration and with the possibility to reset it to its original state (Part I(2)(b)).
- Limited attack surface. Each unit exposes only the external interfaces its function needs (Part I(2)(j)).
- Security updates. Vulnerabilities can be fixed through security updates, and updates are distributed through a secure mechanism (Part I(2)(c) and Part II(7)).
- Data in transit. Data sent over cellular, Bluetooth or V2X links is protected by state of the art encryption (Part I(2)(e)).
- Vulnerability handling. The manufacturer handles vulnerabilities for the full support period (Article 13(8) and Annex I Part II).
also requires a software bill of materials (SBOM) in a commonly used, machine-readable format that covers at least the top-level dependencies of the product.
CVD Policy and Vulnerability Reporting Contact
requires a coordinated vulnerability disclosure (CVD) policy for each in-scope product. Part II(6) requires a contact address for the reporting of vulnerabilities, and Article 13(17) requires a single point of contact that users can find easily. A security.txt file (RFC 9116) is a common way to publish the contact address. The CRA does not prescribe that format.
- The products the policy covers
- The channel for reports, such as encrypted email or a web form
- The acknowledgement time and what reporters can expect
- The remediation and public disclosure process
Vehicle types outside the CRA still need processes to monitor and respond to cyber threats and vulnerabilities under UN Regulation No 155. One public CVD channel can serve both regimes. CVD Portal gives each product line a disclosure portal, a security.txt file, a triage workflow and CSAF 2.0 advisories for resolved vulnerabilities.
Article 14 Incident Reporting for Automotive Vulnerabilities
Article 14 requires the manufacturer of an in-scope product to notify each actively exploited vulnerability and each severe incident that it becomes aware of. The notification goes simultaneously to the CSIRT designated as coordinator and to ENISA, through the single reporting platform. Article 14 applies from 11 September 2026, also to in-scope products placed on the market before 11 December 2027 (Article 69(3)).
- An early warning within 24 hours of becoming aware
- A vulnerability notification within 72 hours
- A final report no later than 14 days after a corrective or mitigating measure is available
For a severe incident, the final report is due within one month of the incident notification. To meet these times, the manufacturer needs exploitation signals from field telemetry, threat intelligence and PSIRT intake. CVD Portal's Article 14 timeline tool tracks each deadline from the moment a report is flagged as actively exploited.
Which conformity assessment route applies?
A default-class product can use Module A, the internal control procedure in which the manufacturer assesses its own product (Article 32(1)). An Annex III Class I product can use Module A only when it fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level substantial or higher (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet. A Class I product therefore needs EU-type examination (Modules B and C) or full quality assurance (Module H) by a notified body for now. A Class II product always needs a notified body or a certification scheme specified under Article 27(9) (Article 32(3)).
ISO/SAE 21434 is not a harmonised standard under the CRA and gives no presumption of conformity. The CRA standards in preparation are the EN 40000 series and the product-specific standards drafted under standardisation request M/606. ISO/SAE 21434 work products, such as a threat analysis and risk assessment (TARA), can still feed the Article 13(2) risk assessment and the technical documentation. Keep a mapping from each work product to the Annex I requirement it supports.
Which Tier-1 supplier products stay in CRA scope?
A Tier-1 supplier is outside the CRA for components designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144. The exclusion covers sales to the vehicle manufacturer and sales to other operators in the automotive supply chain.
The supplier is a CRA manufacturer for a generic component that can go into different types of products. The same applies when a generic equivalent is offered through channels open to the general public. For each in-scope component, the supplier has the full manufacturer obligations. These include the Article 13(2) risk assessment, the technical documentation, the SBOM, vulnerability handling and Article 14 reporting.
A manufacturer that integrates a component from a third party must exercise due diligence so that the component does not compromise the cybersecurity of its product (Article 13(5)). Supply contracts should state the SBOM delivery, the vulnerability notification times and the CVD commitments for each in-scope component.
Work through the CRA for each product in one workspace.
Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Does the CRA apply to vehicles themselves, or only to aftermarket products?+
The CRA does not apply to vehicles under Regulation (EU) 2019/2144 or to components designed and constructed exclusively for integration into those vehicles (Article 2(2)(c)). An aftermarket product is in scope when it is a generic product, or when a generic equivalent is offered through channels open to the general public. Commission guidance C(2026) 5252, points 244 to 246, sets out this component test. Article 2(6) separately exempts spare parts that replace identical components of an in-scope product.
How long must the support period be for an in-scope automotive product?+
The support period must reflect the time the product is expected to be in use, and it must be at least five years (Article 13(8)). A shorter period is allowed only when the product is expected to be in use for less than five years. An aftermarket unit that is expected to stay in a vehicle for its service life needs a support period that reflects that use. The technical documentation must record the information used to set the period. Article 13(19) requires the end date, at least the month and the year, to be clear at the time of purchase.
Can ISO/SAE 21434 certification substitute for CRA conformity assessment?+
No. ISO/SAE 21434 is not a harmonised standard under the CRA, so it gives no presumption of conformity and does not open Module A for an Annex III Class I product. No CRA harmonised standard is cited in the Official Journal yet. ISO/SAE 21434 work products, such as a TARA, can support the Article 13(2) risk assessment and the technical documentation of an in-scope product. Keep a mapping from each work product to the Annex I requirement it supports.
Key CRA articles for Automotive OEMs & Tier-1 Suppliers
Guides for related sectors
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Start a CRA risk assessment for Automotive OEMs & Tier-1 Suppliers
A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.