Secure Boot & OTA Lifecycle

01The Problem

Industrial and medical devices run for 10+ years in the field. Without a secure boot chain, any attacker with physical or network access can flash malicious firmware. Without signed OTA, a man-in-the-middle can push backdoors. The EU CRA (Cyber Resilience Act) now mandates this, non-compliance blocks market access.

02Our Approach

1. 01Hardware Root of Trust: OTP fuses → BootROM signature verification → signed U-Boot → signed kernel
2. 02dm-verity: block-level kernel integrity verification, any tamper kills the system
3. 03LUKS2 encrypted rootfs with TPM2-sealed key derivation
4. 04Mender.io or SWUpdate delta OTA: only changed blocks transmitted, bandwidth optimized
5. 05ISO 27001 DevSecOps: air-gapped signing server, HSM-protected private keys

03Architecture Components

Published measurements are taken on our own bench; the setup and method sit next to the number

To evaluate your Secure Boot & OTA Lifecycle needs on your own platform, schedule an embedded architecture audit or scope your platform class with the system requirements calculator.