Embedded Security's Weakest Link: Lessons From Simple Mistakes
summary
Finds real mistakes: a common engineering password burned into flash and shared across products that can't be changed; leaving test modes and debug pads that let outsiders upgrade or control devices; a tiny UART buffer overflow — ~10–20 bytes — that achieves remote code execution without trace; teams who ignore compiler warnings and return codes; and designers unaware of UK PSTI rules. Offers concrete lab demos, coding habits to fix, and checklist-driven design practices from embedded courses.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:49Who is Duos
- 4:23Weakest link in embedded security
- 6:27Regulations and compliance gaps
- 7:32Security bugs and code quality
- 10:20Code readability and maintainability
- 11:43User input and testing assumptions
- 13:06Simple mistakes and major bugs
- 14:09Dangers of test modes
- 15:13Compiler warnings and frameworks
related talks
35mPatterns and Anti-Patterns in Embedded Development: What Security Incidents...
44mNight of the living vulnerabilities
14mHow not to secure your embedded system, lessons from automotive testing
01h 06mHacking and Securing C++- 35mPatterns and Anti-Patterns in Embedded Development: What Security Incidents...
23mSecure Code, Safe Future: Mastering Security in Critical Software Development
01h 24mCode Red: Navigating the Minefield of Security Programming Blunders
39mNight of the living vulnerabilities