Certified Security and Containerisation for RISC-V Microcontrollers
summary
A minimal PSA-certified TEE for MMU-less RISC-V cores (Zaya) exposes the standard PSA crypto API, uses available hardware virtualization, and runs as an independent security monitor that preserves signature and lifecycle so user updates do not break certification. A user-space runtime hosts isolated microcontainers that are independent executables, enforce explicit resource access policies, allow independent deployment and third‑party certification, and can run interpreters, VMs or RTOS images — the claim is the device attains a PSA-compliant root of trust.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:06Security challenges in RISC-V
- 3:39Requirements for secure systems
- 6:51PSA-certified solution for RISC-V
- 9:25Extending to user space programming
- 11:13Xaya micro-containers overview
- 13:16Access policies for micro-containers
- 14:21Use cases and conclusion
related talks
39mSoftware Supply Chain Security with Trusted Execution Environment Provisioning (T...
16mTrusted RV: Trusted Execution Environment, Secure Coprocessor, and their Program...
45mThe Future of Security is in Open Silicon
23mRISC V Enclaves A Clean Slate Approach To Linux Security
21mTEEP (Trusted Execution Environment Provisioning) on RISC-V
13mRISC-V: Securing the Future of Open Source Computing
01h 05mConfidential Computing for RISC-V-based Platforms
25mRISC V and Meta framework Security Cert Approach for a Secure Connected World
