Trusted Firmware M, Secure Partitioning – Compartmentalization in IoT
summary
Trusted Firmware M implements TrustZone for Armv8-M to isolate secure and non-secure worlds using memory-region protection, isolated secure threads and a Secure Partition Manager (SPM). It ships two concrete models: library model (synchronous secure function calls, low footprint) and thread model (IPC messages, static resources, asynchronous requests). It handles nested non-secure preemption via hardware stacked contexts, notifies SPM of non-secure thread changes, copies and validates mapped buffers during IPC, and proposes solutions like a per-thread secure stack for reentrant NS calls.
AI-written summary · about
chapters (15)
- 0:00IoT compartmentalization challenges
- 1:42Hardware limits for compartmentalization
- 3:30Levels of isolation in IoT security
- 5:21Secure service interactions
- 7:50Non-secure to secure transitions
- 10:44Non-secure context awareness
- 14:28Two programming models in TF-M
- 17:02Thread model interaction
- 21:29Hardware-assisted scheduling
- 25:28Handling multiple secure requests
- 28:00Dedicated secure stacks
- 29:52Secure preemption by interrupts
- 31:44Secure interrupt handling
- 33:54Summary of approaches
- 36:29Q&A on partition implementation
related talks
23mTrusted Firmware M – what’s cooking?
57mTrusted Firmware M : Core and Partition Manager
51mTrusted Firmware M : Secure Storage
41mTrusted Firmware M: Introduction
26mKeynote: Trusted Firmware – Build Security Collaboratively
27mSecuring Arm Servers
08mSecure Debug IoT on v8-M Cortex-M33
24mSecure architectures for the IoT