Developers do care about security: Building a more collaborative path
summary
Argument that developers and security pair up around concrete changes not policies, with examples: Trend Micro moves secret scanning from per-repo agents to an organization-level rollout to avoid hundreds of installs; threat modeling happens early and saves rework; the AWS Well-Architected Tool and Serverless Application Lens become checkpoints; a misconfigured test causes a Cognito billing spike (from ~$500 to ~$5,000) and is fixed to cut costs 87%; a small Lambda wires Trusted Advisor checks into CloudWatch/PagerDuty to surface service quota alerts before outages.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:43Recap
- 1:11What do developers think
- 3:15Security experts developers
- 4:20Predeployment security
- 4:37Building knowledge
- 9:34Post deployment
- 10:13How do we know
- 12:30Operational reviews
- 15:45AWS WellArchitected
- 18:09Managing AWS accounts
- 19:50AWS security tools
- 25:18Other security tools
- 25:37Auditing Appliance
- 31:31Networking and data
- 33:43Wrap up
- 34:05Outro
related talks
46mAre Developers the New Front Line of Security?
15mHelping security and developers to understand one another
27mDevelopers Struggle with Application Security (and How to Make ...)
54mFrom App Security to Dev Security – Shift left with GitHub Advanced Security
38mSecuring the Cloud
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
36mHow to build continuous security and embed it in your product
52mLeveraging Psychological Needs For Building A Security Culture Amongst Developers