The Hacker’s Perspective: Zephyr OS and On-Device Runtime Protection
summary
Claims a deployable on-device runtime protection for Zephyr that installs by adding a directory and a few CMake lines with Kconfig control, detects exploitation via an “exploitation fingerprint” (memory protection, control-flow integrity, anti-exploitation) and reports attacked line numbers and addresses, and claims to have <3% CPU overhead and ~7% code-size increase with ~5KB memory in some builds. Cites tooling gaps (static analysis misses ~50% of bugs, 70% of weekly patches are memory issues) and says the protection stopped real exploits in tests.
AI-written summary · about
related talks
23mKeynote: Zephyr & IoT Security
46mSecurity in Zephyr and Fuchsia
35mZephyr OS Memory Protection
27mZephyr and Trusted Execution Environments
35mZephyr OS Memory Protection
27mZephyr and Trusted Execution Environments
40mZephyr Project Security Status
46mInsights from Zephyr Security Audit and Vulnerability Experiences
