DevSecOps: How to Use DevOps to Make You More Secure
summary
Security must stop being a gatekeeper and instead surface actionable visibility and build real-time feedback loops. The concrete moves: turn raw logs into spike/attack graphs that correlate error spikes with attack spikes, run bug bounties alongside focused pen tests, and embed security tooling into dev workflows. Evidence: teams that deploy 20 times a day vs systems that change every 18 months can detect an attacker discovering a vuln and ship a fix before the exploit succeeds.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:49Ownership of Deployment
- 7:18The New Things That Security Needs To Focus on
- 15:31Bug Bounties
- 17:48Problem with Pen Testing
- 24:03The Role of Red Teams
- 24:40Improving the Feedback Loop
- 25:15How Do You Embed the Security Skills into the Teams
related talks
34mDevSecOps: How to Use DevOps to Make You More Secure
33mDevSecOps: How to Use DevOps to Make You More Secure
31mDevOps: You Build It, You Secure It
16mDevOps and Security
01h 02mDevSecOps for Developers: How To Start
39mDevOps: The Return of Security
06mDevSecOps – Security Throughout the DevOps Pipeline
39mThe Path Of DevOps Enlightenment For InfoSec