Contents
SpecificationUptane

Uptane

Uptane Standard for Design and Implementation

Uptane defines how vehicles check that software updates come from trusted sources and are authorized for the intended electronic control unit.

What it is

Uptane is a security framework for delivering software updates to vehicles. Its central idea is that receiving a file is insufficient: the vehicle needs trustworthy evidence about the file and permission to install it on the intended ECU.

The standard defines signed metadata—descriptive information protected by digital signatures—and verification procedures. Separating signing responsibilities helps limit the damage from a compromised server or key. Uptane is a specification that organizations implement, rather than a single software product.

Who it applies to

It serves vehicle manufacturers, ECU suppliers, and update platform providers adopting Uptane. Backend engineers operate repositories and signing services; embedded engineers implement verification in the vehicle.

A Primary ECU coordinates downloads and performs full verification. Secondary ECUs receive updates through a Primary and perform full or partial verification. Partial verification accommodates constrained devices, with reduced protection. These responsibilities must be allocated explicitly rather than assuming a gateway makes every downstream ECU trustworthy.

What it covers

The framework separates two repository responsibilities:

Component Purpose
Image repository Describes available software images through signed metadata.
Director repository Authorizes images for particular ECUs using vehicle inventory information.

Root, Targets, Snapshot, and Timestamp roles divide responsibility for trusted keys, image descriptions, metadata consistency, and freshness. Verification checks signatures, expiration, versions, and image hashes and sizes. Secure time and retained security state help prevent acceptance of stale information. The standard also defines ECU version reporting. Uptane Standard

How it fits with other documents

Uptane builds on The Update Framework, adapting secure update concepts to vehicles. Its Deployment Best Practices provides complementary operational advice. A POUF—Protocols, Operations, Usage, and Formats—records implementation choices so cooperating systems can interoperate.

For an engineering team, Uptane can support the secure delivery part of a wider update management process associated with UN R156 and ISO 24089. Adopting it does not by itself demonstrate compliance with those documents. Safety assessment, installation sequencing, A/B partition switching, and recovery remain responsibilities of the surrounding vehicle update design.

In practice

Start by documenting each ECU’s verification capability, initial trusted metadata, keys, storage, and secure time source. Agree supplier signing responsibilities and the implementation profile before integrating clients and repositories.

Plan signing operations, metadata renewal, key rotation, and recovery from compromise as continuing operational work. Test expired metadata, invalid signatures, interrupted downloads, and vehicles returning after long offline periods. Record clear failure reasons for service teams.

An authentic, authorized update can still contain faulty software. Combine Uptane verification with release validation and a controlled installation and recovery process. Treat these deployment choices as part of the update system’s design review. Deployment guidance

What it means for your discipline

  • Software update & OTACore

    Own the update workflow across repositories and vehicle clients. Ensure metadata verification, ECU targeting, reporting, and failure handling follow the specification.

  • CybersecurityCore

    Define signing authority, trust provisioning, key protection, and compromise recovery. Review whether deployment choices preserve Uptane’s security assumptions.

  • HPC & application softwareCore

    Implement and validate repository services and ECU verification clients. Handle malformed metadata, persistent security state, and verification failures correctly.

  • E/E architecturePartial

    Allocate Primary and Secondary ECU responsibilities and define trust boundaries. Account for connectivity, secure time, storage, and supplier interfaces.

  • Base softwarePartial

    Integrate the verification client with cryptographic services, persistent storage, and the bootloader or installation service. Preserve security state across resets.

  • Hardware & siliconPartial

    Provide sufficient processing, memory, and protected storage for the chosen verification approach. Support the platform’s key protection and time requirements.

  • Functional safetyPartial

    Coordinate update acceptance with safe installation conditions and recovery behavior. Authentic software still needs separate safety assessment.

  • Networks & communicationPartial

    Support metadata and image delivery through gateways and vehicle networks. Account for bandwidth and interruptions when planning update distribution.

  • Diagnostics & lifecyclePartial

    Connect verification errors and installed-version information to service troubleshooting. Coordinate ECU replacement and reprogramming with trust provisioning.