The Road To Being Rugged
summary
A 12-person DevSecOps team builds self-service scanners and APIs, runs all security in AWS (S3, EMR, CloudFormation templates) and abandons Splunk for big-data ingestion across 1400 AWS accounts, finding workloads show a new vulnerability roughly every ten days. The embedded security model fails at scale with 3,000 developers, so compliance becomes Git-backed markdown and tickets, grading apps A–F in real time, and weekly Red Team Monday exercises plus an internal blue team close the loop.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:19The case for change
- 7:38Defining DevSecOps
- 12:55Security through automation
- 17:24Communication and metrics
- 22:25Integrating security into DevOps
- 25:51Red team and compliance
- 29:25Blue team and monitoring
- 30:59Data-driven security
- 34:43Future trends and conclusion
related talks
43mBuilding a Secure DevOps Pipeline
31mDevSecOps, or How to Integrate Security into DevOps Practices
37mDevelop and implement a successful DevSecOps approach
53mGround Truths of a Rugged DevOps Practitioner
07mCI/CD Evolution: Ensuring Security and Overview During Rapid Growth
48mHow practical is “DevSecOps” really? – A field report
57mBuilding a Modern Security Engineering Organization
21mPlatform Security