EU Cyber Resilience Act Guide for Connected Vehicle Platform & V2X Vendors
Default class unless the core functionality matches an Annex III category. Annex III has no telematics or V2X category.
Connected vehicle telematics units, V2X units and fleet devices are in CRA scope unless they are designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144 (Article 2(2)(c)). Aftermarket devices sold through channels open to the general public and V2X roadside units are in scope. Annex III has no telematics or V2X category, so these products are default class unless their core functionality matches a listed category.
Last updated 26 October 2026
Which connected vehicle products are in CRA scope?
A connected vehicle product is in CRA scope unless it is designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144. Article 2(2)(c) excludes products to which that Regulation applies. The Regulation covers vehicles of categories M, N and O and the systems, components and separate technical units designed and constructed for them. Commission guidance C(2026) 5252, points 244 to 246, makes the design of the component the test. The exclusion covers sales to the vehicle manufacturer and sales to other operators in the automotive supply chain.
Three groups of products stay in scope. Generic devices that can go into different types of products are in scope, for example an OBD-II dongle or a fleet tracker sold in open retail. A generic equivalent offered through channels open to the general public is in scope whatever the stated intended use. V2X roadside units are road infrastructure equipment. They are not vehicle components, so the vehicle exclusion does not apply to them.
Software follows the same rule. Software designed only for integration into a vehicle system is excluded with that system. Standalone software sold through open channels, such as a fleet app that users install, is in scope. A web platform accessed only through a browser is generally not a product with digital elements, unless it is the remote data processing solution of an in-scope product.
Which CRA class applies to telematics and V2X products?
Annex III lists no telematics, V2X or vehicle category in Class I or Class II. Classification follows the core functionality of the product (Article 7(1)), and Implementing Regulation (EU) 2025/2392 gives the technical description of each category. An aftermarket telematics unit, a V2X retrofit unit or a V2X roadside unit is therefore default class unless its core functionality matches a listed category.
Class II covers hypervisors and container runtime systems, firewalls, intrusion detection and prevention systems, and tamper-resistant microprocessors and microcontrollers. A V2X roadside unit is in Class II only when its core functionality is one of these. A unit whose core functionality is to route traffic to the internet can be a router under Class I point 12. A modem or a secure element inside the unit does not by itself change the class of the unit.
Technical Security for V2X and Telematics Products
Connected vehicle telematics and V2X products are mobile and physically accessible. They connect to the vehicle network and to public cellular or short-range radio networks at the same time. Annex I Part I applies on the basis of the Article 13(2) risk assessment. For these products, the assessment usually leads to the controls below.
- Authentication of V2X messages, for example with the ETSI ITS security framework and its PKI (Part I(2)(d) and (f))
- Encryption of telematics data sent to cloud backends (Part I(2)(e))
- Protection against physical tampering where the risk assessment shows that need
- Authenticated firmware updates that cannot start without authorisation (Part I(2)(c) and (f))
- Separation between the vehicle network interface and the external connectivity interface (Part I(2)(j) and (k))
- Access controls that stop unauthorised access to vehicle location and diagnostic data (Part I(2)(d))
requires a software bill of materials (SBOM). List the device firmware, the cellular modem firmware and the V2X protocol stack components in it.
CVD Policy Requirements for Connected Vehicle Products
requires a coordinated vulnerability disclosure (CVD) policy, and Part II(6) requires a contact address for vulnerability reports. Article 13(17) adds a single point of contact that users can find easily. For connected vehicle products, the CVD policy should cover four points.
- A dedicated channel for security reports
- Reporter timelines that match common automotive disclosure practice, often 90 days
- How vehicle owners, fleet operators and OEM customers get security update notices
- How the vendor works with road operators when a V2X vulnerability affects road safety
Vendors that supply telematics platforms to fleet operators should also state how a fleet operator learns about a vulnerability that affects its vehicles.
Article 14 Incident Reporting for Connected Vehicle Products
Article 14 requires an early warning within 24 hours after the manufacturer becomes aware of an actively exploited vulnerability or a severe incident in an in-scope product. The notification goes simultaneously to the CSIRT designated as coordinator and to ENISA, through the single reporting platform. A fuller notification follows within 72 hours. For a vulnerability, the final report is due no later than 14 days after a corrective or mitigating measure is available.
For connected vehicle products, exploitation can mean fleet data exfiltration, vehicle tracking by unauthorised parties or, in the worst case, remote manipulation of vehicle systems through the telematics interface. For a V2X roadside unit, exploitation can affect traffic signal communications. Incident response procedures must assess the exploitation across the deployed fleet inside the 24-hour window. When a V2X vulnerability affects road safety, also tell the road and transport authorities.
Which conformity assessment route applies, and where does ISO/SAE 21434 fit?
A default-class telematics or V2X product can use Module A, the internal control procedure (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, so a Class I product needs a notified body (Modules B and C, or Module H) 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 the ETSI ITS security standards are not CRA harmonised standards either. Applying them gives no presumption of conformity and does not open Module A for a Class I product. The CRA standards in preparation are the EN 40000 series and the product-specific standards drafted under standardisation request M/606.
Evidence from ISO/SAE 21434 and UN Regulation No 155 work still helps. A threat analysis and risk assessment (TARA), cybersecurity management system records and security test reports can feed the Article 13(2) risk assessment and the technical documentation. The CE marking must be on the product before it is placed on the EU market.
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
We supply telematics software to an automotive OEM who integrates it into new vehicles as part of the infotainment system. Are we subject to the CRA?+
Software designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144 is outside the CRA (Article 2(2)(c)). This applies to sales to the vehicle manufacturer and to sales to another operator in the automotive supply chain (Commission guidance C(2026) 5252, points 244 to 246). The OEM handles vehicle cybersecurity under the type-approval rules, so your contract should still cover SBOM delivery, vulnerability notification and security update support. If you also sell the software as a generic product through channels open to the general public, for example for retrofit or fleet use, those sales are in CRA scope.
Our OBD-II telematics dongle connects to any vehicle via the OBD port. How do we address CAN bus security risks?+
A dongle that fits any vehicle and is sold to the general public is in CRA scope. The CAN bus has no message authentication and was not designed for hostile use. Annex I requires you to address the risks that your product brings through the CAN bus interface, on the basis of the Article 13(2) risk assessment. The product should not send unauthenticated commands to the CAN bus, and it should block the injection of arbitrary CAN frames. Keep the CAN bus interface separate from the external cellular interface. The user information should state which vehicle systems the product can access. The risk assessment in the technical documentation must address the CAN bus interface, with its controls and the residual risk.
How do the CRA security update requirements apply to telematics units installed in vehicles that may be active for 10–15 years?+
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 expected use time is less than five years. A telematics unit that is expected to stay in a vehicle for 10 to 15 years therefore needs a support period that reflects that use. Article 13(19) requires the end date, at least the month and the year, to be clear at the time of purchase. Budget for update infrastructure for the full period. Before support ends, tell customers early and give them a path forward, such as unit replacement or network isolation of the unsupported devices.
Key CRA articles for Connected Vehicle Platform & V2X Vendors
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 Connected Vehicle Platform & V2X Vendors
A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.