White paper: Root of Trust in the software-defined vehicle

White paper

Software defines premium: the 7 Pillars of lifecycle control

Diadrom's 7 Pillars framework in full: traceability, innovation, uptime, usable management systems, service, secure updates and sustainability.

Viktor Eliasson · 12 min read

Read the white paper
  1. 2026-10-16Root of Trust in the software-defined vehicleState of the art in automotive cybersecurity: secure boot, OTA and A/B swap, access control and key management. What works, what it costs, what is still open.
  2. 2026-10-12ISO 14229-1:2026: what the new UDS edition changes, and what it does notThe fourth edition of the UDS application layer replaced the 2020 edition in June 2026. What changed, what did not, and what to update in specs and test suites.
  3. 2026-10-12UN R156 01 series: an RXSWIN for every approval you updateThe 01 series of amendments to UN R156 has applied since June 2026. What it requires of RXSWIN, the transitional dates, and what it means for engineering.
  4. 2026-08-31Delete the word “vehicle” and this report is about your product tooA reading of the APC UK report on Software Defined Vehicle value chains, and why nearly all of it applies to any long-lived product with software in it.
  5. 2026-07-28On-board vs off-board: deciding which side a function belongs onComparing on-board and off-board is easy; deciding is not. Four questions settle which side a diagnostic function belongs on, and what a wrong call costs.
  6. 2026-07-26RXSWIN across ECU variants: easy to define, hard to keep trueWhat is RXSWIN? The UN R156 software identification explained, and how to keep it true across thousands of ECU variants: scoping, the baseline and drift.
  7. 2026-07-23UN R156 compliance: what the SUMS actually requiresUN R156 compliance explained: what the software update management system (SUMS) requires: certificate, RXSWIN, update integrity, the record and EU deadlines.
  8. 2026-07-17Off-board diagnostics and ECU flashing: choosing a toolchain, not just a toolEvaluating an off-board diagnostics and ECU flashing toolchain for serial production: OEM security, obsolescence, takt time, variants and the update record.
  9. 2026-07-07What H SystSäk 2022 asks of suppliersThe Swedish Armed Forces' system safety handbook from the supplier's seat: the SSPP, the analysis chain, the risk log and the SCA — and where the work starts.
  10. 2026-07-07ISO 26262 vs MIL-STD-882E: same discipline, two worldsHow automotive functional safety (ISO 26262, ASIL) and defence system safety (MIL-STD-882E, H SystSäk 2022) differ — risk models, software rigour, evidence.
  11. 2026-07-06ISO 24089: software update engineering, explainedWhat ISO 24089 requires of an engineering organisation — from organisational processes to packages and campaigns — and how it connects to UN R156.
  12. 2026-07-06UN R155 CSMS requirements and the diagnostic channelHow UN R155 and CSMS requirements land on the diagnostic channel: Annex 5 threats, UDS SecurityAccess, secured DoIP and the evidence type approval demands.
  13. 2026-07-02ECU flash programming over UDS: how reflashing actually worksThe UDS reprogramming sequence step by step — sessions, security access, erase, transfer, verify — and what a production-grade flash bootloader must guarantee.
  14. 2026-07-01Controlled AI for mission-critical diagnosticsWhy AI is only trustworthy in mission-critical systems when it sits on a provable diagnostics foundation — and what controlled AI looks like in practice.
  15. 2026-06-28Automating UDS diagnostic verification in CI and on HILWhy diagnostics must be re-verified on every change, and how to automate UDS regression, DTC logic, ODX consistency and flash in CI and on HIL rigs.
  16. 2026-06-28DoIP and ISO 13400: diagnostics over IP explainedWhat is DoIP? Diagnostics over IP (ISO 13400) explained: vehicle discovery over UDP, TCP routing activation, and why UDS runs unchanged on Ethernet.
  17. 2026-06-28ECU baseline, variant coding and configuration managementVariant coding explained: how ECU variant coding, the baseline and configuration management keep the as-designed and as-built state of every variant in step.
  18. 2026-06-28Off-board vs on-board diagnostics: where the engineering livesOff-board vs on-board diagnostics explained: the external tester side, the standards (UDS, ODX, DoIP) involved, and why the durable engineering lives off-board.
  19. 2026-06-28Securing the diagnostic channel: ISO 21434, UN R155 and UDS 0x29UDS 0x29 Authentication explained, and why ISO/SAE 21434 and UN R155/R156 move vehicle diagnostics from 0x27 SecurityAccess to certificate-based PKI.
  20. 2026-06-28SOVD vs UDS: diagnostics for the software-defined vehicleWhat is SOVD? How service-oriented vehicle diagnostics (ASAM, ISO 17978) differs from UDS, and why the two coexist in the software-defined vehicle.
  21. 2026-06-28Through-life defence diagnostics for long-life systemsDefence platforms outlive their silicon, tools and people. Tool-independent, standards-based through-life diagnostics keep them ready across decades.
  22. 2026-06-28UDS protocol (ISO 14229) explained: a guide to the servicesWhat the UDS protocol (ISO 14229) is and how it works: sessions, security access, the flash sequence, negative responses, and the UDS stack on CAN and DoIP.
  23. 2026-06-28What is ODX? The ISO 22901 diagnostic data layer, and PDXODX meaning: what ODX (ISO 22901 / ASAM MCD-2 D) is, how it relates to UDS, what PDX packaging is, and why keeping ODX in sync with the ECU matters.
  24. 2026-06-22Abstracting the HSM: portable security for the bootloaderWhy a hardware abstraction layer over the HSM keeps automotive bootloader security portable, unit-testable and resilient to silicon-vendor change.
  25. 2026-06-22Automotive AI is only as good as the data it learns fromGenerative AI has run low on fresh data. In the vehicle the next edge is not a bigger model but real, contextual data — from the software-defined vehicle.
  26. 2026-06-22The EU Data Act: the first domino of the software-defined vehicleWhy the EU Data Act, applicable since September 2025, is the regulatory trigger for the software-defined vehicle — and what it means for carmakers.
  27. 2026-06-22Taming the software-defined vehicle with diagnosticsThe software-defined vehicle multiplies complexity faster than teams can test it. Diagnostics is the control plane: one source of truth, one tool chain.

Newsletter

One email a month. Nothing else.

Subscribe to Diadrom Insights