Developer Productivity Shouldn’t Breach Security
summary
Cloud misconfigurations and leaked credentials drive real breaches: Samsung exposes 7,000 secrets, Toyota accidentally publishes data for 290,000 customers, and crypto.com loses ~$30M. A demo reveals the Kudu console exposing app settings and connection strings. Practical fixes are concrete: put secrets in Azure Key Vault, use managed identities and per-environment service principals, enforce least-privilege RBAC, use private endpoints + Azure Firewall/Front Door/API Management, run CI/CD with self-hosted agents inside a VNet, and use PIM for just-in-time elevated access.
AI-written summary · about
chapters (10)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 1:18Introduction to Developer Productivity vs. Security
- 5:21The Risks of Exposed Secrets and Misconfigurations
- 10:56Using Azure Key Vault and Managed Identities for Secret Management
- 15:23Implementing Role-Based Access Control and Security Best Practices
- 20:56Handling Cloud Networking Security with Virtual Networks
- 25:04The Importance of Secure Development and Continuous Monitoring
- 30:10Real-World Security Pitfalls in Developer Environments
- 35:29Securing APIs and Using Azure Active Directory
- 40:17Security and Network Considerations for Cloud-Based Applications
related talks
45mKeeping Your AI/ML Data Secure
57mCloud’s Dirty Little Secret: It Was Misconfigs All Along
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
22mDevSecOps - The Story of 3 Security Breaches
26mCloud Security Lessons
25mSecuring Your DevOps Transformation
46mSecrets Management for the Modern Tech. Pro
07mDon't Go There! Horrible Devops Security Blunders