From Bugs to Breaches: How to be a Security Tester
summary
Personal story of becoming automotive security testers focuses on concrete takeaways not promises: cites nearly 300 incidents (50% increase year over year), details a real CAN injection on Toyota R4 that unlocks doors and starts the engine in minutes, lists standards applied like UNECE R155 and ISO 21434, names tools such as Vector tools and protocol fuzzing, describes building special in‑house test equipment and trips to production plants to fix issues under time pressure.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:09Security testing in automotive
- 4:00Security testing process
- 6:05Security vs traditional testing
- 7:54Early security tester challenges
- 10:19Real-world demands and isolation
- 13:53Becoming a security tester
- 15:26Q&A: Ethical hacking vs testing
- 16:28Q&A: Preventing security issues
- 17:12Q&A: Automotive security tools
- 18:17Q&A: Manual vs automated testing
- 18:58Q&A: Validation basis
- 19:42Q&A: Time for security testing
- 20:47Q&A: Automotive security example
- 21:49Q&A: Tools for beginners
related talks
36mCar Hacking
12mConfessions of a reformed pentester
37mAutomatic Automotive Hacking
43mSecuring the Connected Car
57mFinding, Managing, Preventing Vulnerabilities: An Automotive Perspective
27mHow to Start Security Testing Without Fear
44mApplication Security: Everything we know is wrong
41mTest Smarter Security Essentials for Quality Engineers