EU Cyber Resilience Act Guide for Fleet Management & Telematics Vendors
Default class unless the core functionality matches an Annex III category, such as a router or a modem intended for the connection to the internet (Class I point 12).
Fleet management and telematics vendors that place OBD dongles, trackers, gateways or installable fleet software on the EU market must comply with the EU Cyber Resilience Act. Units designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144 are excluded (Article 2(2)(c)). Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. Annex III has no telematics category, so telematics hardware is default class unless its core functionality matches a listed category.
Last updated 26 October 2026
CRA Scope and Classification for Telematics Products
Fleet management hardware, such as OBD-II dongles, CAN bus gateways, satellite tracking units, tachograph remote download devices and trailer telematics units, is in CRA scope when it is a generic product or a generic equivalent is sold through channels open to the general public. A unit designed and constructed exclusively for integration into vehicles under Regulation (EU) 2019/2144 is excluded by Article 2(2)(c). The exclusion also covers sales to other operators in the automotive supply chain (Commission guidance C(2026) 5252, points 244 to 246). A fleet platform that includes installed hardware or an app that users install is in scope for those elements.
Annex III has no category for telematics or for products that connect to a vehicle network. Classification follows the core functionality of the product (Article 7(1)). A telematics unit 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). A cellular modem inside the unit does not by itself make the unit important. Access to the CAN bus or the OBD port raises the risk, and the Article 13(2) risk assessment must address it. That access does not change the class.
Annex I Technical Requirements for Telematics Hardware
Telematics hardware vendors must address Annex I requirements that account for the vehicle-network interface and cellular connectivity of their products:
- Authenticated CAN/OBD access: Where a telematics device reads from or writes to vehicle CAN bus systems, access must be authenticated and the device must not accept commands from unauthorised sources that could be passed to the vehicle network.
- Cellular communication security: All data transmitted over cellular networks (MQTT, HTTPS, proprietary protocols) must be encrypted with current TLS standards. Certificate pinning should be considered for high-security applications.
- Firmware update authentication: OTA firmware updates to telematics hardware must be cryptographically signed. Update delivery over cellular must verify integrity before installation.
- Data minimisation: Telematics devices must not collect or transmit data beyond what is necessary for the declared fleet management function.
- Remote wipe/disable: If the telematics device processes sensitive fleet or driver data, a mechanism for remote data wipe upon device loss or end-of-service must be provided.
CVD Policy and Article 13 for Telematics Vendors
Fleet management vendors serve commercial vehicle operators - logistics companies, bus operators, construction fleets - whose operations depend on the integrity and confidentiality of telematics data. Security vulnerabilities in telematics hardware or platforms can expose route planning data, driver behaviour records, and vehicle location information that has significant commercial sensitivity.
- Define the scope of covered products (hardware and software)
- Provide a submission channel for fleet operator security teams and independent researchers
- Commit to customer notification for vulnerabilities that could expose fleet operational data
- Address vehicle security implications - vulnerabilities that could affect vehicle systems (via OBD interface) must be treated with elevated urgency and coordinated with vehicle OEMs where relevant
CVD Portal enables telematics vendors without dedicated security teams to establish a standards-compliant CVD programme through the intake, triage, and advisory publication workflow.
Article 14 Incident Reporting for Fleet Telematics
Article 14 applies when a telematics vulnerability is being actively exploited. For fleet management vendors, exploitation scenarios include mass location data exfiltration, fleet route manipulation, and in rare cases, vehicle system interference via the OBD interface. The 24-hour early warning to the CSIRT designated as coordinator and to ENISA must be built into incident response procedures.
Some fleet operator customers are essential or important entities under NIS2, for example postal and courier service providers. They have their own incident reporting obligations under Article 23 of Directive (EU) 2022/2555. Telematics vendors should be prepared to provide fleet operator customers with the technical information they need to fulfil their own NIS2 reporting obligations, in addition to filing the Article 14 CRA report. The coordination between vendor CRA reporting and operator NIS2 reporting should be pre-agreed as part of commercial contracts and security incident response plans.
Conformity Assessment and Vehicle Cybersecurity Standards
A default-class telematics product can use Module A, the internal control procedure (Article 32(1)). A product whose core functionality matches an Annex III Class I category needs a notified body for now, because no CRA harmonised standard is cited in the Official Journal yet (Article 32(2)). ISO/SAE 21434 is not a harmonised standard under the CRA and gives no presumption of conformity.
- The vehicle interface security design (CAN bus access controls, OBD communication security)
- Cellular communication security architecture
- OTA update security mechanism
- SBOM for firmware and software components
- CVD policy and operational status
Vendors with products subject to the tachograph rules (Regulation (EU) No 165/2014 and amendments) should make sure that the CRA conformity assessment covers the tachograph interface components. These components have additional security requirements under the tachograph rules.
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
Are insurance telematics (UBI) devices subject to the CRA?+
Yes. Usage-based insurance (UBI) telematics devices, such as OBD dongles that collect driving behaviour data for insurance pricing, are products with digital elements within CRA scope when they are placed on the EU market as hardware products. A UBI device is default class unless its core functionality matches an Annex III category. An OBD interface or cellular connectivity does not by itself make it an important product. Driving behaviour data, such as harsh braking and cornering forces, is personal data when it relates to an identifiable driver, so the GDPR applies in parallel with the CRA. also requires the device to process only data that is adequate, relevant and limited to what its intended purpose needs.
Does a fleet management platform (pure SaaS, no hardware) require CRA compliance?+
A fleet management platform that the vendor only offers as SaaS, with no hardware and no installed software, is outside CRA scope. NIS2 can apply to the vendor as a cloud computing service provider, listed in Annex I to Directive (EU) 2022/2555, when the vendor is a medium-sized or larger enterprise. A mobile app or an installed desktop component of the platform is a product with digital elements. When the vendor also supplies connected hardware, such as an OBD dongle or a gateway, the hardware is in scope. The cloud platform is remote data processing under Article 3(2) when two conditions are both met. The vendor designed and developed the platform, or had it developed under its responsibility. Without the platform, the hardware cannot perform one of its functions. Remote data processing is part of the product and must meet Annex I. Vendors should do a scope assessment for each product offering.
How do we handle CRA compliance for third-party OBD hardware we resell under our brand?+
If you place a third-party OBD device on the EU market under your own brand name, you are the manufacturer for CRA purposes, regardless of who physically manufactures the hardware. This means you are responsible for CRA conformity, including obtaining technical documentation from the original manufacturer, verifying Annex I compliance, maintaining an SBOM, establishing a CVD policy, and providing security updates throughout the product's declared supported lifetime. White-labelling arrangements must be reviewed and updated to ensure the original manufacturer provides the security documentation and ongoing support you need to fulfil your CRA manufacturer obligations.
Key CRA articles for Fleet Management & Telematics 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 Fleet Management & Telematics Vendors
A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.