DevSecOps: How to Use DevOps to Make You More Secure
summary
Built security program at Etsy while the org moves from monthly releases to 20 deployments a day and shifts the role of security from gatekeeper to enabler of teams. Advocates surfacing security like APM — centralized logs, dashboards and alerts — and integrating defenses into the toolchain (slack alerts, auto-file Jira tickets, CI hooks). Uses pen tests plus continuous feedback from bug bounty reports, with one real case where an attacker is detected and a fix ships before an exploit emerges.
AI-written summary · about
chapters (21)
- 0:00Intro
- 3:46Whats Changed
- 5:54The Biggest Takeaway
- 7:42New Concepts
- 8:11DevOps Lessons
- 8:42Security Visibility
- 10:17Improving Security Visibility
- 11:06Security Visibility for Everyone
- 12:14What Does This Mean
- 14:17Two Lessons Learned
- 15:54Bug Bounty
- 17:35Pen Tests
- 18:02Success Story
- 19:57DevOps Makes Us More Secure
- 21:00DevOps Makes Us Safer
- 21:27How Do We Get Visibility
- 21:37Questions
- 21:51DevSecOps vs Security
- 23:39How to Get Started
- 25:24Budget Shifts
- 28:34Bounty Stories
related talks
34mDevSecOps: How to Use DevOps to Make You More Secure
27mDevSecOps: How to Use DevOps to Make You More Secure
01h 02mDevSecOps for Developers: How To Start
31mDevSecOps, or How to Integrate Security into DevOps Practices
57mBuilding a Modern Security Engineering Organization
16mDevOps and Security
06mDevSecOps – Security Throughout the DevOps Pipeline
39mThe Path Of DevOps Enlightenment For InfoSec