Modern Least Privilege and DevSecOps
summary
Argues that modern least privilege needs concrete practices: adopt repair, repave, rotate as a default lifecycle, generate and consume software bills of materials (SBOM) so teams know what’s in artifacts, and replace long‑lived secrets with short‑lived cryptographic identities tied to unique service identities rather than shared credentials. Recommends platform teams embed these controls programmatically, use immutable repaved infrastructure, and aim for just‑in‑time credentials and point‑to‑point mutual TLS/zero‑trust enforcement.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 2:54Book on DevSecOps transformation
- 4:21What won't change in security
- 7:13Reality of software vulnerabilities
- 10:24Path forward with the 3Rs
- 13:39Least privilege in modern systems
- 17:35Zero trust and identities
- 20:50DevSecOps and rapid deployment
- 22:36Conclusion and key takeaways
related talks
09mKeynote: Modern Least Privilege and DevSecOps
31mLeast Privilege In The Age of Thinking Machines
17mKeynote: Modern Least Privilege with DevSecOps
32mRugged Building Materials & Creating Agility with Security
42mMaking Security Approachable for Developers and Operators
57mHow Do I Secure My Micro-Services?
01h 17mSecure by Design - Security Principles for the Working Architect
57mMaking Security Priority Zero