Secure Boot and Firmware Updates

Threat models, roots of trust, signed images and update systems that survive attackers and power cuts.

Design connected devices that only run your firmware and can be updated safely for years. Learn threat modelling, the cryptography a firmware engineer needs, roots of trust and secure boot, debug lock-down and lifecycle states, robust A/B updates with rollback protection, signing key management, open-source tools and the main security regulations.

Advanced · 5 modules · 18 lessons · free certificate

About this course

A connected device sits in the attacker's hands, runs for years and is often one of thousands built from the same image. If an attacker can make it run their code, read its keys or install an old vulnerable release, every unit in the field is exposed. This course explains how to stop that. It starts with a practical threat model, teaches the cryptographic building blocks at the level needed to use vetted libraries correctly, and then builds a chain of trust from an immutable boot stage through to the application.

You will work through image signing and verification, key storage in one-time programmable memory and secure elements, TrustZone and measured boot at a concept level, debug and readout protection, device lifecycle states and factory provisioning. The update modules cover A/B and swap-based slot layouts, rollback protection, power-fail safety, delta updates, delivery over Bluetooth Low Energy or the network, signing in the build pipeline and staged rollouts. The final module describes MCUboot, Trusted Firmware-M, Mender, SWUpdate and RAUC neutrally, and orients you to ETSI EN 303 645, the EU Cyber Resilience Act, the US Cyber Trust Mark, the NIST IR 8259 baseline, SBOMs and vulnerability disclosure.

Out of scope: implementing cryptographic algorithms, penetration testing technique, cloud back-end and web application security, and legal advice on any regulation. The bootloader basics covered in Embedded Firmware Fundamentals are assumed and taken much further here. A course certificate records completion only and is not a security certification.

Before you start: You should be comfortable writing firmware in C for a microcontroller or embedded Linux system, and understand flash memory, linker layouts and what a bootloader does. Embedded Firmware Fundamentals in the AAVICO Academy covers that background. No prior cryptography or security experience is assumed.

What you will learn

  • Build a threat model for a connected device and turn it into concrete security requirements
  • Choose and use hashes, MACs, authenticated encryption and digital signatures correctly, without writing crypto yourself
  • Design a chain of trust from an immutable boot stage, with suitable key storage, debug lock-down and lifecycle states
  • Design a power-fail-safe update system with rollback protection, signed images and a staged rollout
  • Plan signing key management, factory provisioning and the tools to implement them
  • Explain what ETSI EN 303 645, the Cyber Resilience Act, NIST IR 8259, SBOMs and disclosure policies expect of a device maker

Who it is for

  • Firmware engineers who own the bootloader, update path or security features of a connected product
  • Embedded Linux engineers designing verified boot and over-the-air update systems
  • Hardware engineers choosing microcontrollers, secure elements and debug access for production boards
  • Technical leads and product owners who must plan security support and regulatory readiness

Syllabus

Module 1: Threat Modelling for Connected Devices

Why embedded security is different, what you are protecting, who attacks devices and through which surfaces, and how to turn that into requirements.

  1. Why Device Security Is Different
  2. Assets, Attackers and Attack Surfaces
  3. Running a Threat Model and Writing Requirements
  4. Module quiz (5 questions)

Module 2: Cryptography a Firmware Engineer Needs

Hashes, MACs, symmetric and public-key cryptography, digital signatures, authenticated encryption and random numbers, at the level needed to use vetted libraries correctly.

  1. Hashes, CRCs and Message Authentication Codes
  2. Symmetric Keys, Public Keys and Digital Signatures
  3. Why Encryption Is Not Authentication
  4. Random Numbers, Entropy and Key Generation
  5. Module quiz (5 questions)

Module 3: Root of Trust, Secure Boot and Device Lock-down

Immutable boot stages and the chain of trust, verifying images robustly, storing keys in OTP, secure elements and TrustZone, and locking debug access through lifecycle states.

  1. The Root of Trust and the Chain of Trust
  2. Verifying Images Robustly
  3. Key Storage: OTP, Secure Elements and TrustZone
  4. Debug Protection and Lifecycle States
  5. Module quiz (5 questions)

Module 4: Firmware Update Design

Slot layouts and swap strategies, rollback protection and power-fail safety, delivery over the network and Bluetooth Low Energy, delta updates, staged rollouts, and signing and provisioning in the pipeline.

  1. Slot Layouts and Swap Strategies
  2. Rollback Protection and Power-Fail Safety
  3. Delivering Updates: Network, BLE, Deltas and Staged Rollouts
  4. Signing Keys, the Build Pipeline and Factory Provisioning
  5. Module quiz (5 questions)

Module 5: Tools, Regulation and Security Maintenance

Open-source bootloaders and update frameworks, the main security standards and regulations for connected products, SBOMs, vulnerability disclosure and supporting a fleet for years.

  1. Open-Source Building Blocks
  2. Standards and Regulation for Connected Products
  3. SBOMs, Vulnerability Disclosure and Long-Term Support
  4. Module quiz (5 questions)

Free downloads for this course

Enrol for free

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.