Safety vs Security: A Tale of Two Updates
Talkat Open Source Summit Europe + Embedded Linux Conference Europe 2019 · on Monday, 2019-10-28· at 16:20· Forum 3·
summary
Embedded devices lock into safety rules that make updates costly: recertification often takes 6 months to certify, teams see products with 5–20 year lifetimes and support needs that outlast original hardware, and one known avionics workaround requires a reboot every 140 days. Security demands rapid patching, unique per-device keys and signed boot, and a robust rollback-capable updater because a failed upgrade can brick a device. Practical mitigations are containers hypervisors hardware separation and automating certification to create a fast security-only recertification path.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:30Warnings
- 3:16Safety
- 13:05Embedded Systems
- 19:02Security
- 24:42Security updates
- 26:49Critical vs Proactive
- 27:30Product vs Security
- 28:35Recertification
- 30:15Containers and hypervisors
- 32:16Planning
related talks
15mDevice Security Matters More Than Ever
17mAccelerating Development and Deployment of Updatable Linux-based Edge AI devices in the CRA era
27mIoT: What will security standards and certification look like ten years from now?
43mOTA Updates in the Wild: Lessons from the Field
40mThe Need to Drive Towards Frequent and Sustained Software Updates
41mUnique Challenges Of Security Programs For Hardware/IoT Makers
07mIndustrial Security and Environmental Resilience: A Conversation
05mSecurity, Availability, and Multiple Information Sources: Exploring Update Behavior