Practical steps for creating safer software (Code included)
summary
Cybercrime grows far faster than expected with forecasts from about $445B to $2T then $6T and reality worse, and the talk gives concrete developer actions: shows Java code that uses a serialized object to call the docker CLI which can be subverted to run `cat /etc/passwd` and write output to a web file, demonstrating a real exploit that works; highlights dependency confusion, automated fuzzing and botnets, 140,000 GitHub hits for all‑trusting trust managers, build tool attacks via Jenkins/GitHub Actions, and the push for software bill of materials (SBOMs).
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 4:09Why security matters now
- 7:59Prevention: Taking security seriously
- 26:44Prevention: Dependencies and secrets
- 39:07Detection: Spotting abnormal behavior
- 46:29Detection: Logging and error handling
- 49:43Mitigation: Designing safer systems
- 57:30Future: Software bills of materials
- 1:03:47Summary and key takeaways
related talks
41mThe Divine and Felonious Nature of Cyber Security
45mBuilding Secure Software: Practical Strategies for Developers
46mThe Anatomy of Java Vulnerabilities
26mSmarter Code, Sneakier Risks: Supply Chain Security in the Age of AI
56mA New Hope for 2023? What Developers Must Learn Next
32mBreaking the Chain: Advanced Offensive Strategies in Software Supply Chain
34mThe Simple, Yet Lethal, Anatomy of a Software Supply Chain Attack
26mStranger Danger: Your Attack Surface Just Got Bigger