Insights
How we think about ECU security.
Practical writing from the team that builds AutoST: how the attacks work, how the tests work and how to fit them into real development.
Android IVI security checks every head unit should pass
Hardening checks for an Android head unit: build type, debug flags, ADB exposure, SELinux, exported components, app flags and secrets, and what each means.
Oct 7, 2026 · 7 min read
Choosing a CAN interface for ECU security testing
What matters in a CAN interface for security testing: SocketCAN vs Vector XL, CAN FD, timing control and error-frame visibility, and how to pick one for your bench.
Oct 7, 2026 · 8 min read
DoIP test setup: from Ethernet link to UDS over IP
A practical DoIP bench setup: addressing, vehicle discovery, routing activation and running UDS over IP, with the byte-level exchanges you need to get a link up.
Oct 7, 2026 · 9 min read
ECU reset and session handling bugs, and how to test them
How to test UDS session and reset handling: session fallback, S3 timeout, security state after reset, TesterPresent keeping a session alive, and what each result means.
Oct 7, 2026 · 7 min read
How to write an ECU security test plan
How to structure an ECU security test plan: scope, bench, test cases traced to the TARA, pass criteria in bytes, ordering by risk, and the evidence to keep.
Oct 7, 2026 · 7 min read
Finding hidden diagnostic services on an ECU
How undocumented UDS services, sessions and DIDs are found by probing and reading response codes, why they exist, and what a hidden service means for the attack surface.
Oct 7, 2026 · 7 min read
ISO/SAE 21434 verification evidence from security testing
What counts as verification evidence under ISO/SAE 21434, which clauses ask for it, and how to turn a security test run into an artifact an assessor accepts.
Oct 7, 2026 · 9 min read
ODX-driven testing: turn your diagnostic data into tests
How ODX and PDX files drive a sharper ECU security test: what a DIAG-LAYER names, how DIDs and routines come from the data, and why that beats brute force.
Oct 7, 2026 · 8 min read
SecOC testing from the bus side: what a tester can check
How to test AUTOSAR SecOC without the keys: freshness and MAC on the wire, replay and reorder behaviour, truncated MAC length, and what each result means.
Oct 7, 2026 · 8 min read
SecurityAccess seed/key weaknesses and how to test them
The common ways a UDS SecurityAccess (0x27) gate fails: constant seeds, no lockout, keys derivable from the seed, and a non-destructive method to test each one.
Oct 7, 2026 · 9 min read
SOME/IP security testing: what to check and why
How to test SOME/IP on the bench: build a service inventory from service discovery, compare it to the matrix, check who can reach each service, and read results.
Oct 7, 2026 · 7 min read
TARA step by step: a worked threat analysis for an ECU
How to run a TARA under ISO/SAE 21434: asset identification, threat scenarios, attack paths, feasibility and risk, worked through for a single diagnostic ECU.
Oct 7, 2026 · 10 min read
A UDS fuzzing methodology that finds real bugs
How to fuzz an ECU over UDS without wasting runs: where to inject, how to detect a crash, how to make a finding reproducible, and how to stay on the bench.
Oct 7, 2026 · 9 min read
UDS negative response codes explained for testers
What a UDS negative response (0x7F) tells you on the bench: the structure, the codes that matter during enumeration and SecurityAccess, and how to read them.
Oct 7, 2026 · 8 min read
UN R155 audits: what testers need to deliver
What a UN R155 assessment expects from the test side: traceable test cases, versioned evidence, coverage, clean results, residual risk and supplier deliverables.
Oct 7, 2026 · 7 min read
What an ECU pentest report should contain
The sections an ECU pentest report needs so developers can fix and assessors can trace: scope, bench, reproducible findings, severity, evidence and re-test.
Oct 7, 2026 · 8 min read
Too few security engineers: automation, AI and reaching SOP clean
There are not enough automotive security specialists to test every ECU on every release. AI-driven automation is how a small team still reaches SOP clean.
Oct 2, 2026 · 8 min read
Traceability in an ISO 21434 audit: making fuzzing count
Security testing is required by ISO/SAE 21434, but tests only pass an assessment when they are traceable. Here is what an assessor looks for and how to get there.
Oct 1, 2026 · 9 min read
UDS enumeration explained: how to map an ECU safely
What UDS enumeration finds on an automotive ECU, why sessions and services matter, and how a non-destructive scan maps the diagnostic surface without breaking anything.
Oct 1, 2026 · 7 min read