Are Developers the New Front Line of Security?
summary
Panel asserts developers must own specific security tasks: threat modeling in design, pipeline automation, and external pen tests that actually audit the supply chain. Cites a 100:10:1 developer to ops to security ratio, the Codecov compromise, and ~16–20% of cloud breaches from misconfigured storage. Recommends hands‑on workshops, retrospectives on real pen test findings, automated in‑pipeline alerts, and a mandated software bill of materials so teams can trace dependencies and reduce supply‑chain risk.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:51Developers' evolving security role
- 8:02Developer-centric security education
- 13:15Balancing developer and security needs
- 21:03Codecov breach lessons
- 26:01Software supply chain security
- 33:03SBOM impact on teams
- 41:27On-premise vs cloud security
- 44:41Summary
related talks
27mDevelopers Struggle with Application Security (and How to Make ...)
52mHow to Transform Developers into Security People
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
31mDevOps: You Build It, You Secure It
01h 02mDevSecOps for Developers: How To Start
47mSecurity is Everybody's Job
34mDevelopers do care about security: Building a more collaborative path
45mSo Happy Together: Making the Promise of DevSecOps a Reality