Balancing Developer Fre...
summary
Describes concrete fixes for container sprawl and CVE load: standardizing base images, generating software bill of materials for every artifact, and using admission controller policies to block stale images in registries; shows a real vulnerability named Tarmagdon and the mess of a fork‑of‑a‑fork dependency chain; gives platform patterns (baked security, automated license and SBOM pipelines), operational advice (smaller images, design for fast recovery) and practical tradeoffs for open source maintenance and developer velocity.
AI-written summary · about
chapters (7)
- 0:00Balancing dev freedom and security
- 3:58Security vs developer freedom tension
- 10:46Balancing freedom and security possible
- 16:22Security or developer freedom
- 18:27Open source security challenges
- 22:45Tips for balancing freedom and security
- 25:39Audience questions and closing remarks
related talks
38mSo. Many. Vulnerabilities. Why are containers such a mess...
25mA Primer on Software Bill of Materials for DevSecOps
22mUsing Buildpacks To Reduce Container Bloat and Attack Surface
42mSponsored Session: Dependencies: Do's and Don'ts
34mCloud Native Security 101: Building Blocks, Patterns and Best Practices
28mCode, Dependencies and Security: Where Is the Risk
41mIdentifying and Mitigating Cloud and Container Threats
23mDEVOPS DAYS MTL 2018 - Tsvi Korren