Securing Your DevOps Transformation
summary
Organizations get 95% of cloud breaches from human configuration mistakes and 85% of defects are introduced in code, so the talk shows concrete fixes: use Dependabot, CodeQL and secret scanning in GitHub; adopt VS Code Spaces for locked-down developer environments; push ARM or Terraform as infrastructure as code into CI/CD pipelines with Azure DevOps, Azure Policy and Azure Key Vault; add Azure Monitor and the Secure DevOps Kit for Azure for alerting. Uber’s 57 million‑user breach and months‑long Capital One detection illustrate why these measures matter.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:18Why is DevOps important
- 3:49We all make mistakes
- 12:14How do we secure our DevOps journey
- 12:49Enabling secure development
- 13:29Device security
- 15:16Source control
- 18:35CICD tooling
- 19:58Monitoring learning
- 21:37Azure
- 23:48Secure DevOps Toolkit
- 24:25Conclusion
related talks
55mWhat you need to know about security for cloud DevOps
52mImplement DevSecOps in Azure
42mAzure DevOps security - Lessons learned
31mDevOps: You Build It, You Secure It
39mDevOps: The Return of Security
25mKeynote: DevOps - The Return of Security
44mAzure DevSecOps
49mAzure DevOps security - Lessons learned