Proving RISC-V Security Model Compliance with SESIP
summary
Shows how SESIP maps the RISC‑V Platform Security Model to a reusable catalog of security features and a corresponding C1–C5 evaluation levels regimen that increases verification effort from document review to white‑box pentesting; assessment focuses on remote attacks by default with optional physical‑attack claims. Component evaluations get combined via component result reuse so a RISC‑V root‑of‑trust can be assessed once, integrated with others, and NXP reports applying the profile to its RISC‑V products with certificates accepted by PSA Verified for RFC 8259A.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:32Context-loT security ecosystem complexity
- 1:26Context - compliance demonstration needed
- 2:43Security platform's role in device security requirements
- 3:45Challenge - compliance demonstration comple
- 5:16What SESIP brings
- 6:43SESIP composition and reuse details
- 7:35Mappable and accessible security features
- 9:29Adapted attack contexts
- 10:45RISC-V & SESIP mappability overview
- 12:39Relevant security leveling
- 14:36Core MCU/MPU SESIP Profile
- 16:23Conclusion
related talks
25mRISC V and Meta framework Security Cert Approach for a Secure Connected World
13mRISC-V: Securing the Future of Open Source Computing
19mAn Open Source Approach to System Security
18mCPU Security in the Context of RISC-V
45mVerified seL4 on secure RISC-V processors
16mKeynote: RISC-V Security - Current Initiatives and Future Trends
09mThe Future of Embedded Security with RISC-V
21mRISC-V International Security Overview
