DevSecOps: How to Use DevOps to Make You More Secure
summary
Security shifts from gatekeeper to enabler by proving fixes fast and surfacing real risk: run focused static analysis in CI (start with command execution and grep-based checks), flag when encryption or auth code appears, allow emergency changes but page owners, use continuous crawlers to catch TLS regressions and reintroduced XSS, combine bug bounties with targeted pentests, unify logs and error graphs for correlated alerts, and remember Etsy deploys roughly 20 times a day versus legacy 18‑month release cycles.
AI-written summary · about
chapters (13)
- 0:00Intro
- 7:44Agenda
- 8:47Static Analysis
- 12:38Static Analysis for Policy
- 18:21Dynamic Scanning
- 18:36What is Dynamic Scanning
- 19:02How to Adapt Dynamic Scanning
- 22:05Security Visibility
- 22:58Example of Security Visibility
- 24:39Feedback
- 25:18Bug bounties
- 27:49Why DevOps makes us more secure
- 32:47Wrapping up
related talks
33mDevSecOps: How to Use DevOps to Make You More Secure
27mDevSecOps: How to Use DevOps to Make You More Secure
31mDevOps: You Build It, You Secure It
01h 02mDevSecOps for Developers: How To Start
39mDevOps: The Return of Security
31mDevSecOps, or How to Integrate Security into DevOps Practices
06mDevSecOps – Security Throughout the DevOps Pipeline
31mWhy SecDevOps is the new way in Cybersecurity?