Securing the Connected Car - Opportunities and Security Risks

Securing the Connected Car - Opportunities and Security Risks

Linux Foundation via YouTube Direct link

Why security patching happens too late

13 of 19

13 of 19

Why security patching happens too late

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Securing the Connected Car - Opportunities and Security Risks

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Session overview
  3. 3 Software defined car: New revenue streams
  4. 4 Cost savings by using open source platforms
  5. 5 The software defined car requires OTA updates
  6. 6 Jeep Cherokee hacked in July 2015
  7. 7 Jeep Cherokee Head Unit with Wifi
  8. 8 Wifi-based breach: Short-range
  9. 9 The Controller Area Network (CAN) bus
  10. 10 Putting it together
  11. 11 More complexity leads to larger attack surface
  12. 12 Security patching is done too late
  13. 13 Why security patching happens too late
  14. 14 Patching connected devices is harder
  15. 15 Generic embedded updater workflow
  16. 16 Choice of update type has tradeoffs
  17. 17 Strategies to reduce the risk of bricking
  18. 18 Prepare for securing the software defined car
  19. 19 The best way to respond to hacking?

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.