DevOps is Now DevSecOps
summary
Survey data shows 58% of respondents are decision-makers and 31% still ask what is DevSecOps, while 62.5% call it a cultural shift not merely tools. Top roadblocks are time and resources; 43% find security earliest at code, 34% at the SDLC pipeline. Recommendations are concrete: secure the CI/CD pipeline, run software composition analysis and SBOMs for the software supply chain, harden Kubernetes, and seed teams with security champions to reduce alerts and close flaws.
AI-written summary · about
chapters (9)
- 0:00Introduction and conference overview
- 4:22DevSecOps evolution and definitions
- 9:24Cultural shift from Waterfall to DevOps
- 15:50Legacy systems and technical debt
- 21:45DevOps pipeline hardening and trends
- 28:57Securing cloud-native Kubernetes environments
- 33:40Critical aspects of DevSecOps
- 40:59Developer fatigue and security champions
- 47:20Summary and next steps for DevSecOps
related talks
23mDevSecOps - By Any Other Name
53mDevSecOps Next: Navigating the Next Era with Industry Titans
36mHow to Turn DevOps into DevSecOps
39mDevSecOps: What, Why and How
38mDevSecOps - what does it mean and where is it taking us?
06mDevSecOps is a Misnomer
04mThe relationship between DevOps and security
39mDevOps: The Return of Security
