Trusted Firmware M : Secure Storage
summary
Trusted Firmware M implements a secure-storage prototype with a custom flash file system, a compile-time policy-based access table, and a crypto-backed key derived from a hardware unique key. It enforces that keys never leave the crypto service by using reference access for opaque object use, and guarantees power-fail safety by writing encrypted object data to a scratch block then swapping metadata with a signed swap counter—an atomic updates scheme. Rollback protection is not yet implemented; the design targets highly constrained, customizable IoT devices.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:30Agenda
- 1:15What is Saracen
- 2:20Secrets
- 3:16CI
- 6:54Filesystem
- 7:25Assets
- 8:13Secure Storage
- 9:39Policy Manager
- 11:30Reference Access
- 14:15Difference Access
- 15:46File System
- 21:03Motivation
- 22:17Flows
- 22:32Key derivation
- 23:15Secure service operation
- 24:48System requirements
- 27:24Metadata
- 33:28Not Simplified view
- 37:30API List
- 38:26File System Design
related talks
23mTrusted Firmware M – what’s cooking?
39mTrusted Firmware M, Secure Partitioning – Compartmentalization in IoT
39mTrusted Firmware M, Secure Partitioning – Compartmentalization in IoT
43mDevice Security in IoT
26mKeynote: Trusted Firmware – Build Security Collaboratively
45mBuilding a Secure IoT Device
41mTrusted Firmware Project update
39mSecuring firmware: Secure and Trusted boot in OpenBMC