Panel: From Code to Defense: Why Developers Are the New Security Leaders
summary
A claim that insecure code costs about $4.5M per breach drives a concrete shift left: teams build dedicated DevSecOps squads and a new product line, embed security into CI/CD so unsafe commits block like compile errors, and add runtime checks and chaos testing. A purchased SCA sandboxing feature fails for a year, so static analysis is fine tuned and combined with runtime validation, cutting false positives and friction. Secrets management and PII detection get automated, and LLMs are used only for risk scoring not mass code generation.
AI-written summary · about
chapters (18)
- 0:00Introduction and panel setup
- 1:06Security ownership evolution
- 3:54DevSecOps team integration
- 5:39Shifting left for scalability
- 8:47Balancing security coverage
- 10:53Overcoming developer obstacles
- 14:05Empathy in security practices
- 15:29Security vs development speed
- 19:25Effective developer training
- 23:32Managing tool fatigue
- 28:32Automation success stories
- 31:01AI's role in security
- 35:59Step-by-step security maturity
- 39:13Organizational culture impact
- 40:17Security is a continuum
- 42:27Teaching security to developers
- 43:10Security professionals learning development
- 47:46Personality and training in security
related talks
54mFrom App Security to Dev Security – Shift left with GitHub Advanced Security
46mAre Developers the New Front Line of Security?
47mSecurity is Everybody's Job
31mDevOps: You Build It, You Secure It
49mFrom Application Security to Developer Security
45mBuilding Secure Software: Practical Strategies for Developers
51mSecurity & Privacy in Digital First Businesses (Panel)
27mDevelopers Struggle with Application Security (and How to Make ...)