← CRA Compliance Checklists
AutomotiveDeadline: 11 December 2027

CRA Compliance Checklist: Automotive Electronics & In-Vehicle Systems

Excluded for vehicles under Regulation (EU) 2019/2144 and for components designed exclusively for them. Generic and open-channel automotive electronics are in scope and are default class unless their core functionality matches an Annex III category.

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)). Generic automotive electronics, and generic equivalents sold through channels open to the general public, are in scope whatever the stated intended use. OBD-II dongles, diagnostic tools and fleet telematics devices sold in open retail are examples. Map each product to its design and its sales channel.

15
checklist items
15
high priority
11 December 2027
deadline
Automotive
sector
CRA Classification:Excluded for vehicles under Regulation (EU) 2019/2144 and for components designed exclusively for them. Generic and open-channel automotive electronics are in scope and are default class unless their core functionality matches an Annex III category.

Last updated 26 October 2026

1. Scope & Classification

Decide for each product whether it is designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144

highArticle 2(2)(c), CRA

Article 2(2)(c) excludes products to which Regulation (EU) 2019/2144 applies, including systems and components designed and constructed for those vehicles. Commission guidance C(2026) 5252, points 244 to 246, make the design of the component the test. The exclusion covers sales to the vehicle manufacturer and to other operators in the automotive supply chain. Record the decision and the evidence for it, such as restricted business-to-business sales channels.

Identify generic products and open-channel sales, such as OBD dongles, fleet trackers and retrofit infotainment sold to the general public

highArticle 2(1), Article 3(1), CRA

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 is in scope whatever the stated intended use.

Classify each in-scope product by its core functionality against Annex III and Annex IV

highArticle 7(1), Annex III

Annex III has no category for vehicle safety functions, ADAS, gateway ECUs or V2X modules. An in-scope product is default class unless its core functionality matches a listed category, such as a router or a modem intended for the connection to the internet (Class I point 12). Implementing Regulation (EU) 2025/2392 gives the technical description of each category.

Compile SBOM for all in-scope automotive electronics covering ECU firmware, AUTOSAR layers, middleware, and telematics software

high

Automotive software stacks are complex: AUTOSAR BSW, middleware, application software, and telematics. All must be tracked. Align with SBOM requirements emerging from automotive industry standards (NTIA, ISO/SAE 21434).

2. Product Security (Annex I Part I)

Implement secure boot and code signing for all ECU firmware - prevent unauthorised firmware loading

high

Secure boot is a fundamental automotive cybersecurity control. Align with ISO/SAE 21434 requirements and UNECE R155/R156 obligations. Hardware Security Modules (HSM) in ECUs should hold signing keys.

Implement authentication and integrity protection for all OTA software update packages

high

OTA updates to vehicle software must be cryptographically signed and verified before installation. UN R156 provides detailed requirements for software update management systems.

Implement network segmentation within the vehicle using a gateway ECU - isolate safety-critical networks from infotainment and telematics

high

Vehicle networks (CAN, LIN, Ethernet) must be segmented. The central gateway must enforce strict domain separation between powertrain, chassis, safety, and infotainment domains.

Encrypt all external communications - V2X, telematics, remote diagnostics, and OTA - using appropriate automotive cryptographic standards

high

External vehicle communications must be encrypted. V2X uses IEEE 1609.2 PKI. Telematics and OTA use TLS. Align with ETSI ITS and SAE J3101 specifications.

3. CVD Policy & Vulnerability Handling

Put in place, enforce and publish a CVD policy, and align it with ISO/SAE 21434 vulnerability management

high, Annex II(2), CRA / ISO/SAE 21434 clause 8

ISO/SAE 21434 clause 8 covers vulnerability analysis and vulnerability management. A CVD process aligned with that clause can serve the automotive framework and the CRA. CRA conformity still depends on Annex I, Part II, because ISO/SAE 21434 is not a CRA harmonised standard. Annex II, point 2 requires the user information to say where the CVD policy can be found.

Establish a vehicle cybersecurity incident response process aligned with UNECE WP.29 CSMS requirements

high, CRA / UN R155

UNECE R155 requires a Cybersecurity Management System covering incident response. Align your CRA CVD process with your CSMS to avoid duplicate processes.

Set a support period that reflects the expected use time of each in-scope product, at least five years

highArticle 13(8)

The support period must be at least five years. A shorter period is allowed only when the product is expected to be in use for less than five years. Aftermarket units that stay in a vehicle for its service life need a support period that reflects that expected use.

4. Article 14 Incident Reporting

Align Article 14 reporting with UNECE R155 cybersecurity incident reporting to type approval authorities

highArticle 14(2), CRA / UN R155

R155 requires reporting cybersecurity incidents to type approval authorities. CRA Article 14 requires notification to the CSIRT designated as coordinator and to ENISA. Products excluded under Article 2(2)(c) have no Article 14 duty. For in-scope products, Article 14 applies.

Pre-prepare Article 14 notification templates for automotive-specific incidents - focus on safety-critical system compromise and fleet-scale exploitation

highArticle 14(2)

Fleet-scale automotive cyber incidents (e.g. mass OTA compromise) are high-severity Article 14 triggers. Templates should address the fleet dimension - how many vehicles affected, geographic spread.

5. CE Marking & Technical Documentation

For excluded products, keep the R155 CSMS and R156 SUMS documentation and the evidence for the Article 2(2)(c) exclusion

highArticle 2(2)(c), CRA / UN R155 / UN R156

The exclusion follows from Regulation (EU) 2019/2144 and the design of the component. Keep the design and sales channel evidence with the type-approval documentation, so a market surveillance authority can see why the CRA does not apply.

For standalone in-scope automotive electronics, prepare full CRA technical file and issue EU Declaration of Conformity

highArticle 31, Annex VII, Article 28, Annex V

Aftermarket and fleet telematics products must have CRA technical files and DoCs. ISO/SAE 21434 work products, such as a TARA, can feed the risk assessment. ISO/SAE 21434 is not a CRA harmonised standard.

Track your Automotive Electronics & In-Vehicle Systems compliance progress in CVD Portal.

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 OBD-II diagnostic dongles and fleet telematics units?+

Yes, when they are generic products or generic equivalents sold through channels open to the general public. OBD-II dongles and fleet telematics units sold in open retail are in scope. A unit designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144 is excluded (Article 2(2)(c)). Annex III has no telematics category, so these products are default class unless their core functionality matches a listed category.

We are a Tier 1 supplier providing ECUs to OEMs - does CRA apply to us or the OEM?+

ECUs designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144 are outside the CRA (Article 2(2)(c)). The exclusion covers sales to the OEM and to other operators in the automotive supply chain (Commission guidance C(2026) 5252, points 244 to 246). The CRA applies to you as manufacturer for a generic ECU that can go into different types of products, and for a generic equivalent offered through channels open to the general public. OEMs will still require cybersecurity support, SBOMs and vulnerability information from Tier 1 suppliers for their R155 cybersecurity management system.

How does ISO/SAE 21434 relate to CRA compliance for automotive electronics?+

ISO/SAE 21434 is the main automotive cybersecurity engineering standard and overlaps with many Annex I requirements. 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 TARA, can still feed the Article 13(2) risk assessment and the technical documentation of an in-scope product.

This checklist is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Need a CVD policy for Automotive Electronics & In-Vehicle Systems?

Download a free CRA-compliant disclosure policy template and deploy it in minutes.

Browse templates →