Panel: The Right To Secure; What, Who, How And Why!
summary
Panel argues for a practical right to secure: allow owners to patch end‑of‑life embedded gear when vendors refuse, backed by automated firmware analysis and micro‑patching evidence such as DARPA’s work and community tools like the md380 patches that succeeded but revealed hardware variations and test case gaps. Operators report over 50% end‑of‑life devices in production, vendors cite warranty and IP risks, and proposed fixes include contract “marching rights,” automated validation pipelines, and insurer re‑assessment rather than full source disclosure.
AI-written summary · about
chapters (6)
- 0:00Introduction to panel
- 4:00Forever days in critical infrastructure
- 13:36Operational challenges and risks
- 27:41Legal and insurance barriers
- 32:13Marching rights for operators
- 34:19Audience Q&A begins
related talks
44mHardware Security By Design
48mCXO PANEL: Security Certifications for IoT Devices
28mSo You Think You Can Patch
27mSecurity: The Thing That Everyone...
58mSecuring a World of Physically Capable Computers
50mRunning in the Shadow: Perspectives on Securing the Software Supply Chain
41mUnique Challenges Of Security Programs For Hardware/IoT Makers
44mMake It Fixable