Black Friday Our software, PenTest Project: Slate Enterprise at €53 instead of €173 per user a month, and Flint free for 12 months. Until 30 November. See the offer →
PenTest Hub logo

CAN · ECUs · Infotainment · Telematics

Automotive & Connected Vehicle Security Testing

We simulate attacks against connected vehicles: in-vehicle networks, ECUs, infotainment, telematics units and wireless entry points, and the back-end services they connect to, aligned with ISO/SAE 21434 and UNECE R155.

  • CAN, LIN and FlexRay
  • ECUs, infotainment, telematics
  • ISO/SAE 21434 and UNECE R155
Sample findings · Vehicle assessmentSample
CRITICALInfotainment unit can send messages to the vehicle busNo filtering at the gateway
HIGHDiagnostic commands accepted without authenticationReplayed from the OBD port
HIGHTelematics API exposes any vehicle's locationVehicle ID guessable
MEDIUMDebug interface active on an ECUFirmware can be read out
Attack paths across the vehicle and its back endSample findings

In one sentence

What is automotive security testing?

Automotive security testing simulates attacks against connected vehicles, their in-vehicle networks, electronic control units, infotainment and telematics systems and the services they connect to, to find the paths an attacker could use to affect safety, privacy or operation.

Modern vehicles are networks on wheels, connected to apps and back-end services. We analyse attack paths across firmware, APIs, ECUs and external services, for single vehicles and fleet-wide infrastructure.

Who it is for

  • Vehicle manufacturers
  • Tier 1 and tier 2 suppliers
  • Telematics and fleet service providers
  • Companies preparing for type approval

Scope

What we test

The vehicle, its components and the services it connects to.

In-vehicle networks

CAN, LIN and FlexRay: message filtering, authentication and gateway separation.

  • CAN
  • LIN
  • FlexRay

ECUs

Electronic control units: firmware, debug interfaces, diagnostics and secure boot.

  • Firmware
  • Diagnostics
  • Secure boot

Infotainment

Head units and their apps, connectivity and access to vehicle networks.

  • Head units
  • Apps
  • Connectivity

Telematics and back end

Telematics units, mobile apps and the APIs and services behind them.

  • Telematics
  • APIs
  • Mobile apps

Wireless entry points

Bluetooth, Wi-Fi, cellular and other radio interfaces into the vehicle.

  • Bluetooth
  • Wi-Fi
  • Cellular

Fleet infrastructure

Attack paths that could affect many vehicles at once.

  • Fleet
  • Updates
  • Scale

Methods

How we test a vehicle

From individual components to the complete vehicle and its services.

Component

Bench testing

ECUs, head units and telematics units tested on the bench.

System

Vehicle testing

Attacks across in-vehicle networks and wireless entry points on a complete vehicle.

Ecosystem

Back end and apps

The APIs, apps and cloud services connected to the vehicle and fleet.

Engagement

How we work with you

  1. Scope online

    Describe what you need in Flint, our scoping platform. Answer only the questions that apply.

  2. Proposal, signed online

    Effort, price and the statement of work are built from your answers.

  3. Ready for day one

    Authorisation, test accounts and rules of engagement are agreed before testing starts.

  4. Senior-led testing

    Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.

  5. Report and retest

    Your report is ready in Slate, our client portal, within 48 hours of testing ending.

What you receive

Everything stays in one place, in your own client portal.

  • A report in Slate within 48 hours of testing ending
  • Every finding with evidence, a risk rating and a fix
  • An executive summary for leadership
  • Retests you can request finding by finding
  • Downloads as PDF or Excel
  • Evidence you can hand to your auditors

Standards

Standards we test against

Aligned with automotive cybersecurity standards and regulation.

  • ISO/SAE 21434
  • UNECE R155 (WP.29)
  • OWASP IoT Top 10

FAQ

Frequently asked questions

Can't find yours? Ask a senior tester and we'll reply directly.

Do you test complete vehicles or components?
Both. We test components such as ECUs and telematics units on the bench, complete vehicles, and the back-end services they connect to.
Does testing help with ISO/SAE 21434 and UNECE R155?
Yes. It gives you independent testing evidence for your cybersecurity management system and type approval work. It is evidence, not a certification.
What do you need from us?
Components or a vehicle for testing, documentation where available, and access to the relevant back-end environments. We agree this during scoping.
Do you test mobile apps and APIs for vehicles?
Yes. Apps and APIs connected to vehicles are often the easiest way in, so we include them when they are in scope.
When will we receive the report?
Within 48 hours of testing ending, in Slate, our client portal.

Contact

Tell us what you need to test

A senior tester reads every message and replies directly.