Hypervisors and IoT (IoT Secret Storage)
summary
Focuses on how to keep per-device secrets off accessible flash on tiny MCUs so attackers can't read private keys via buffer overflows or memory reads. Compares four practical approaches and tradeoffs: network secret provisioning versus per-device keys, use of TrustZone for Armv8-M, full MMU VM/user‑space separation with Zephyr, a tiny separate CPU holding keys, and a software microvisor hypervisor-ish layer. Recommends prototyping the microvisor, defining a dual‑CPU example (PSA/TFM style), and supporting VM paths where hardware permits.
AI-written summary · about
chapters (12)
- 0:00Introduction to IoT security
- 3:57Need for secure secrets in IoT
- 6:10Hardware-based security solutions
- 9:02Four proposed solutions overview
- 12:14Dual-core CPU approach
- 14:06Recommendations and future work
- 16:15Q&A on TPM and secure storage
- 18:28Production system solutions
- 20:15Software isolation and hypervisors
- 21:20Provisioning challenges in IoT
- 23:17Initial secret provisioning methods
- 25:08Closing remarks and Q&A
related talks
38mBoot to Cloud Security Considerations with IoT
23mKeynote: Zephyr & IoT Security
49mBreaking Hardware-Enforced Security With Hypervisors
38mOne Ring -3 To Secure Them All: Computing with Hardware Enclaves
21mEmbedded solution for multiprocess application
40mKeeping secrets in your opponent's hands
18mIoT Security's Toughest Challenges: Root of Trust, TEEs, & Firmware Updates
27mvTZ: Virtualizing ARM TrustZone