DevSecOps Next: Navigating the Next Era with Industry Titans
summary
Research of a couple thousand respondents and 40,000 article clicks finds less than 20% of orgs doing DevSecOps at scale while ~70% merely dabble; developers spend 11–29% of time actually coding. Recommendations: generate SBOMs early and make them actionable, continuously scan CI/CD pipelines and artifact registries for misconfig and vulnerabilities, build a developer experience that bundles context plus automated remediation, and use AI to prioritize fixes and create safe automatic pull requests rather than flooding teams with alerts.
AI-written summary · about
chapters (7)
- 0:00DevSecOps Next intro
- 5:06Panel backgrounds
- 10:59DevSecOps adoption expectations
- 22:21Three pillars for DevSecOps
- 31:04Software supply chain security
- 38:19AI in DevSecOps future
- 46:37Q&A on licensing and CI/CD
related talks
30mDevSecOps: More Than Just Pipelines
51mDevOps is Now DevSecOps
32mDevSecOps is Dead, Long Live DevSecOps
01h 02mDevSecOps for Developers: How To Start
23mDevSecOps - By Any Other Name
40mDevSecOps Guide to Bulletproof Your Development Workflow
36mUnderstanding the Sec in DevSecOps: Beyond Just Shifting Left
44m10 Attributes of the DevSecOps Elite