Why it exists
If an attacker can replace ECU software, every other protection can be switched off. Secure boot ensures only software signed by the manufacturer runs.
What it is
- A root of trust: immutable code (boot ROM) and a key (or its hash) stored in hardware.
- A chain: each stage verifies the signature of the next before starting it.
- Variants: secure boot (stop if verification fails) and measured/authenticated boot (record measurements; HSM verifies in parallel and may withhold keys).
How it works
Software images are signed in a protected signing environment at the manufacturer. At startup, the boot ROM verifies the bootloader, the bootloader verifies the application, and so on. On HPCs the chain continues through firmware, hypervisor and operating systems.
Example chain; actual stages vary by ECU, and a failed verification prevents the affected stage from starting.
Best practices
- Protect signing keys in an HSM with strict access control.
- Plan key rotation and revocation for the vehicle’s lifetime.
- Disable or lock debug interfaces in production.
- Balance verification time against startup requirements (e.g. parallel verification by the HSM).
Common pitfalls
- Verifying only a checksum, not a cryptographic signature.
- Leaving a downgrade path to older, vulnerable software versions.