Keynote: DevOps - The Return of Security
summary
Argues security must start at day zero of development and be treated as code across source, infra and configs, with concrete tools and checks: Azure DevOps, Jira, Git, Terraform/CloudFormation, Visual Studio/VS Code, SAST/DAST and dependency scans, secret management, fuzzing and load tests, post-deploy scans and quarterly pen tests. Calls out a striking ratio: 100 devs : 10 ops : 1 security making security a bottleneck, and prescribes just-in-time access and just-enough-admin plus automated runbooks to block attackers.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:30Security in DevOps
- 4:33Communication
- 4:50Statistics
- 5:43Training
- 6:51Effective Communication
- 7:42Security as a Code
- 9:29Integration
- 9:49Planning
- 10:30Coding
- 11:49Builds
- 13:05Testing
- 15:55Release and Deploy
- 16:46Security
- 21:19Other Aspects
related talks
39mDevOps: The Return of Security
01h 02mDevSecOps for Developers: How To Start
31mDevOps: You Build It, You Secure It
16mDevOps and Security
01h 04mKeynote: Every Security Team is a Software Team Now
27mDevSecOps: How to Use DevOps to Make You More Secure
27mMulti Security Checkpoints on DevOps Platform
04mThe relationship between DevOps and security