Join our Newsletter — 33% off our NHI Course
Home› Guides› Uptane and Vehicle OTA Security Guide: Compromise-Resilient Software…
Guide OT & IoT Security

Uptane and Vehicle OTA Security Guide: Compromise-Resilient Software Updates for Vehicles

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

An over-the-air update system can reach every vehicle a manufacturer has sold, so a single compromised server or signing key could push malicious software to a whole fleet. Uptane is the open standard designed for that problem: a framework for vehicle software updates that keeps vehicles safe even when part of the update infrastructure has been compromised. This guide explains how Uptane works (roles, the Image and Director repositories, Primary and Secondary ECUs, full and partial verification), which attacks it defends against, how it relates to UN Regulation No. 156 on software update management, and how to deploy it. It is for automotive product security engineers, OTA platform teams, suppliers building ECUs and security leads preparing for type approval. For the wider vehicle security picture see the Connected and Autonomous Vehicle Security Guide.

Key takeaways

  • Uptane assumes compromise. It splits trust across two repositories and four signing roles so that one stolen key or one breached server is not enough to install arbitrary software.
  • Two repositories, cross-checked. The Image repository says what software is genuine; the Director says what each vehicle should install. Full verification requires both to agree.
  • Primaries must fully verify. The standard says "A Primary ECU SHALL perform full verification"; Secondaries perform full verification where possible and partial verification at minimum.
  • Freeze and rollback attacks are first-class threats. Expiring metadata, version numbers that must not decrease and a secure time source on ECUs block them.
  • Uptane helps with R156 but is not R156. UN R156 requires a certified Software Update Management System; Uptane gives strong technical evidence for its integrity requirements.

What Uptane is and its status

The Uptane Standard for Design and Implementation is published at uptane.org; the version marked "Latest" when checked on 27 October 2026 was 2.1.0. The standard builds on The Update Framework (TUF), which it cites for metadata and filename design and for TUF extensions such as TAP-3 (multi-role delegations) and TAP-4 (multiple repository consensus). Uptane adapts TUF to vehicles, where many ECUs are constrained, sit behind a gateway and cannot talk to the internet directly. TUF 1.0.37 itself advises that the Root role key should be kept offline, and lists the attacks TUF protects against, including arbitrary installation, indefinite freeze, mix-and-match, rollback and vulnerability to key compromises.

Roles, repositories and ECUs

The four roles

RoleWhat it signsWhy it is separate
RootMetadata that distributes and revokes the public keys of the other rolesThe trust anchor; used rarely, so it can be kept well protected
TargetsImage metadata such as hashes and file sizesSays which images are genuine; can delegate to suppliers on the Image repository
SnapshotWhich Targets metadata was released togetherPrevents mix-and-match of metadata versions
TimestampWhether new metadata or images existLets ECUs detect freeze attacks cheaply

Each role has a signature threshold, and the standard requires that Root rotation be signed by both the old and the new Root keys.

Image repository and Director repository

  • Image repository: holds images and their signed metadata. The standard describes it as "designed to be primarily controlled by human actors, and updated relatively infrequently". It checks delegation chains before accepting uploads, and only this repository supports delegations, which is how suppliers sign their own ECU images.
  • Director repository: decides which images each vehicle should install. It is "mostly controlled by automated, online processes", consults an inventory database of vehicles and ECUs and signs metadata on demand. It can also encrypt images for ECUs that require it.

The standard assumes the two repositories are not compromised at the same time, and full verification relies on that separation. Run them on separate infrastructure with separate administrators and separate key custody.

Primary and Secondary ECUs

  • Primary: talks to the back end, collects the vehicle version manifest, checks time, downloads and fully verifies metadata, downloads images for itself and its Secondaries, then distributes time, metadata and images to them.
  • Secondary: receives updates through a Primary. It should perform full verification if it can; otherwise it must perform at least partial verification.

Verification and reporting

ModeWhat the ECU checksWhat it protects againstWhen to use it
Full verificationDirector and Image repository metadata, and that their Targets metadata matchCompromise of either repository on its ownRequired on Primaries; preferred on any Secondary with the memory, compute and storage
Partial verificationOnly the Director's Targets metadataTampering in transit and attacks short of Director key compromiseMinimum for constrained Secondaries

Vehicle version manifest: the Primary builds a signed manifest that includes the vehicle identifier, its own identifier and the ECU version reports. Each ECU version report is signed by the ECU and includes the installed image's metadata, any attack the ECU detected, the latest time the ECU could verify and a nonce or counter that changes each update cycle to prevent replay. The Director checks these reports against its inventory before it generates new metadata. ECU identity keys are unique to each ECU.

Attacks Uptane is designed to stop

AttackHow Uptane respondsWhat you must implement
Arbitrary softwareMetadata must carry signatures that meet the role's thresholdThresholds above one for high-value roles
RollbackMetadata version numbers must not decrease and image release counters must not go backwardsPersistent storage of last-seen versions on each ECU
FreezeEach metadata file expires; ECUs compare expiry with trusted time and reject expired metadataA secure time source: the standard says "ECUs SHALL have a secure source of time"
Mix-and-matchSnapshot metadata ties Targets files togetherSnapshot role and consistent publication
Slow retrievalECUs monitor download speed and should report slow transfers to the DirectorDownload monitoring and reporting
Key or server compromiseDuties split across roles and repositories; full verification needs both repositories to agreeSeparate infrastructure and key custody for the two repositories

Uptane compared with simpler OTA designs

Many OTA systems start with a single signing key and a TLS connection to the vehicle. The comparison shows what Uptane adds and why that matters at fleet scale.

QuestionSingle-key signed OTAUptane
What happens if the signing key is stolen?Attacker can sign images every vehicle acceptsAttacker also needs keys from the other repository or role thresholds, and Root can rotate the compromised key
What happens if the update server is breached?Attacker controls what vehicles install, within signed imagesDirector compromise alone cannot install images the Image repository does not list on fully verifying ECUs
Can an attacker hold vehicles on old software?Often undetectedMetadata expiry plus trusted time exposes freeze attacks
Can suppliers sign their own ECU software?Usually via the OEM keyDelegations on the Image repository, limited to the supplier's paths
Does the back end know what is installed?Depends on telemetrySigned ECU version reports in a vehicle version manifest

The cost is operational: more keys to manage, two repositories to run and more metadata to process on ECUs. For a product that will be in the field for a decade or more and that controls safety functions, that cost is usually justified. For constrained IoT products outside the vehicle the IETF SUIT model may be a better fit; see the IoT Secure Firmware Update Guide.

Where identity fits: keys, ECUs and suppliers

Uptane is, at heart, an identity and key management design. Every role key, every supplier delegation and every ECU key is a non-human identity, and the security of the fleet depends on how those identities are held and rotated.

  • Role keys by risk: keys for roles that change rarely (Root, and Targets on the Image repository) can be held offline in HSMs with multi-person approval and signing thresholds. Online roles (Director, Timestamp, Snapshot) need HSM-backed automated signing with tight access and monitoring. The standard describes how each repository is operated rather than prescribing offline storage, so set this policy explicitly.
  • Supplier delegations: delegate each supplier only the image paths for its own ECUs, so one supplier's key cannot sign another supplier's software. See the Code Signing Security Guide.
  • ECU keys: provision unique ECU keys at manufacture, ideally in a hardware security module or secure element on the ECU, and record them in the Director inventory. See the Device and IoT Identity Guide.
  • Back-end credentials: the Director's database, signing service and cloud accounts are high-value targets. The Toyota T-Connect Key Exposure 2022, where a subcontractor published T-Connect source code containing an access key to a customer data server on public GitHub, shows how back-end secrets of connected vehicle services leak.
  • Rotation drills: practise Root rotation (old and new Root keys both sign) and supplier key revocation before you need them. See the Compromised Code Signing Certificate Playbook.

Uptane and UN Regulation No. 156

UN Regulation No. 156 covers software update management for vehicle categories M, N, O, R, S and T. It requires a manufacturer to hold a Software Update Management System (SUMS) certificate of compliance, which an approval authority issues after assessment and which is valid for up to three years unless withdrawn. The points below are from the original 2021 text published by UNECE; check the current consolidated version and any amendments for your markets.

R156 requirement (original text)How Uptane helpsWhat else you need
7.1: protect the update process and delivery system against manipulation and compromiseRole separation, thresholds, two repositories and full verificationOrganisational controls, key ceremonies, back-end security
7.2.1.1: protect updates against compromise and invalid updatesSigned metadata, hashes and sizes, compatibility via Director inventorySecure build pipeline
7.1: uniquely identify software versions and integrity validation data; confirm compatibility with the last known configurationTargets metadata and vehicle version manifestsInventory accuracy and configuration management
7.2.1.2: RXSWIN readable at least through the OBD port and protected against unauthorised modificationNot addressed directlyRXSWIN management and protection
7.2.2.1.1: restore the previous version or reach a safe state after a failed OTA updateReporting of results to the DirectorA/B partitions or recovery on ECUs
7.2.2.1.2, 7.2.2.3, 7.2.2.5: enough power, safe execution, preconditionsNot addressedVehicle state checks and update orchestration
7.2.2.2 and 7.2.2.4: inform users before and after updatesNot addressedHMI and customer communication

R156 works alongside UN R155 and ISO/SAE 21434 on cybersecurity management. See the ISO/SAE 21434 Automotive Cybersecurity Engineering Guide and the Automotive Cybersecurity Guide.

Implementation roadmap

  1. Map the vehicle architecture: list every updatable ECU, its compute and storage, whether it can do full verification, and how it is reached from the Primary. Use the result in your TARA.
  2. Design key custody: decide offline and online roles, thresholds, HSMs, ceremonies and supplier delegations. Write the Root rotation procedure now.
  3. Stand up separate repositories: Image and Director on separate infrastructure, accounts and administrator groups.
  4. Choose a secure time source: pick a demonstrably secure external time source and test freeze detection by serving expired metadata.
  5. Implement on ECUs: full verification on the Primary; full or partial on Secondaries; persistent storage for last-seen metadata versions; unique ECU keys.
  6. Test attack cases: rollback, freeze, mix-and-match, wrong-ECU image, expired metadata and a revoked supplier key, on a test bench and in pilot vehicles. Interrupt power and connectivity during updates to prove recovery.
  7. Roll out in waves: engineering fleet, employee vehicles, then a small percentage of customers, with Director campaigns that can be halted. Keep a known-good release ready to deploy forward if a campaign fails.
  8. Evidence for type approval: keep design documents, test results and update records in the form your approval authority expects for the SUMS assessment.

Decision guidance: an OEM with a small number of capable ECUs can require full verification everywhere. Vehicles with many low-end ECUs will rely on partial verification for some, so put the most safety-relevant functions on ECUs that can fully verify. Suppliers should support both modes so OEMs can choose. Smaller manufacturers may use a commercial or open source Uptane implementation, but key custody and repository separation remain their responsibility.

Detection and measurement

  • ECU version reports: alert on reports of detected attacks, unexpected installed images or stale verification times.
  • Signing activity: log every signature by every role; alert on Image repository uploads outside release windows or by unexpected delegations.
  • Director anomalies: campaigns created outside change control, or Director metadata targeting images the Image repository does not list.
  • Slow retrieval reports: clusters may point to network interference.

Metrics:

  • Percentage of updatable ECUs performing full verification.
  • Time from security release to 90% fleet installation.
  • Update failure and recovery rates per campaign.
  • Number of signatures outside the approved release process (target zero).
  • Days since the last successful key rotation drill for each role.

Framework mapping

Uptane elementNIST SP 800-53 Rev. 5NIST CSF 2.0
Signed metadata and image hashesSI-7, SI-7(15), CM-14PR.PS-02
Role keys, thresholds and rotationSC-12 Cryptographic Key Establishment and ManagementPR.DS-01
Unique ECU identity keysIA-3 Device Identification and AuthenticationPR.AA-03
Supplier delegationsSR-4 Provenance, SR-11 Component AuthenticityGV.SC-05
Version reports and monitoringSI-4 System MonitoringDE.CM-09
Recovery after failed updatesSC-24 Fail in Known StateID.AM-08

Common failure patterns

  • One server, two repositories: running Image and Director on the same platform or under the same administrators removes the separation full verification depends on.
  • Partial verification everywhere: choosing partial verification on ECUs that could fully verify gives up resilience to Director compromise.
  • No trusted time: without a secure time source, expired metadata cannot be detected and freeze attacks succeed.
  • Broad supplier delegations: a supplier key allowed to sign any path can sign software for ECUs it does not make.
  • Treating Uptane as the whole of R156: user information, safe-state handling, power checks and RXSWIN still need their own design.
  • Weak back-end secrets: leaked cloud or API keys give a route into the systems that run the repositories.

Practitioner checklist

  • Image and Director repositories run on separate infrastructure with separate administrators and key custody.
  • Each role has a defined threshold, storage location and rotation procedure.
  • Primaries perform full verification; each Secondary's verification mode is documented and justified.
  • ECUs have a secure time source and reject expired metadata.
  • ECUs store last-seen metadata versions persistently and reject rollbacks.
  • Supplier delegations are limited to their own image paths.
  • Rollback, freeze, mix-and-match and power-loss tests run on every major release.
  • ECU version reports feed monitoring and incident response.
  • R156 requirements outside Uptane's scope have named owners and evidence.

Standards and references

Related NHI Mgmt Group resources: Connected and Autonomous Vehicle Security Guide · IoT Secure Firmware Update Guide · ISO/SAE 21434 Automotive Cybersecurity Engineering Guide · Code Signing Security Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.