So who owns the security of the IoT
summary
Researchers exploit a carrier link to hijack a vehicle, reprogram the V850 controller and control doors, climate and acceleration; a manufacturer sends a USB-stick patch that transfers ownership to owners. Home audit finds 74 devices, some auto-updating, some unpatched for six months; TPMs often shipped but never enabled. Proposal: move responsibility up the supply chain with measurable SLAs, vendor league tables for days-to-patch, hub or ISP-delivered monitoring services and open standards that allocate end-to-end security duties.
AI-written summary · about
chapters (18)
- 0:00IoT security ownership
- 1:15Industrial IoT and OT
- 3:24IT versus engineering approaches
- 5:14Closed systems vs IoT ecosystems
- 7:01Vehicle security vulnerabilities case study
- 8:50End user IoT security responsibility
- 10:57Service provider IoT security role
- 13:03Chip/device manufacturer duties
- 14:51Why IoT systems lack security
- 16:35Securing IoT ecosystems challenge
- 17:59Hubs for IoT security?
- 19:04Industry standards initiatives
- 20:09Supply chain security cascade
- 21:30IoT security leadership framework
- 22:53Resilient IoT systems design
- 24:00End-to-end supply chain security
- 24:43New IoT security engineering vision
- 25:04Conclusion and call to action
related talks
21mIndustrial IoT security issues and countermeasures
41mPanel: Tackling Automotive Hardware Vulnerabilities
40mSecuring the Connected Car
22mSecuring IoT for Life: Navigating the Challenge of Constant Change
30mSupply Chain Security for IoT Devices
39mDilemma in IoT Access Control: Revealing Novel Attacks and Design Challenges in Mobile-as-a-Gateway
43mSecuring Software-Defined Vehicles: From Threat Awareness To Holistic Cybersecur...
29mSecuring IoT/OT Against Modern Threats