Crypto Agility by Design: Securing PQC with Updatable HW/FW Co-design
summary
Argues that hardware/firmware co‑design lets devices evolve: field-updatable firmware protects expensive PQC hardware, enables SCA patching, parameter tweaks and algorithm migration without physical recall. Cites Checkm8 as a boot‑ROM example of unpatchable failure and the ROA TPM incident where updatable devices receive fixes but non-updatable chips force an 18‑month, global replacement campaign; claims hundreds of millions of affected devices and shows an updatable approach actually mitigates real exploits.
AI-written summary · about
chapters (11)
- 0:00Conference overview
- 1:08Static to dynamic security shift
- 3:20Static defenses dangers
- 5:52Costs of immutability in hardware and firmware
- 7:18Dynamic defense advantages
- 8:26PQC standards and challenges
- 10:15HW/FW co-design for crypto agility
- 11:43Static defenses fail in PQC
- 12:48Q&A: Updating crypto verification
- 14:57Q&A: Certification challenges
- 16:20Q&A: Fixing ASICs in field
related talks
13mEnabling Crypto Agility by Immunizing Processors Against the Exploitation of Software Bugs
40mHardware Cryptographic Modules
27mQuantum-Safe Secure Boot: How hard can it be?
41mPreparing for and migrating to a world with PQC
33mExtending or Evolving: Choosing the Path to Quantum Readiness
14mHow not to secure your embedded system, lessons from automotive testing
27mProtecting Data In-Use from Firmware and Physical Attacks
21mSoK: Where’s the “up”?! A Comprehensive (bottom-up) Study on the Security of...