The Fifth Element : Azure Secure DevOps
summary
Claims that security must be the “fifth element” across design build deploy and ops; uses STRIDE/DREAD threat modeling and the free TMT thread modeling tool to generate mitigation checklists; demonstrates a checked‑in connection string detected by GitHub credential scanning; recommends Azure Key Vault, Security Intelligence extensions for VS/Code, WhiteSource Bolt, Snyk and SonarQube in CI pipelines; shows ARM Template Toolkit, Azure policies/blueprints and Azure Defender image scanning to gate deployments and prevent leaks or crypto‑mining abuses.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:35About Mike
- 2:03Agenda
- 2:43Security Development Lifecycle
- 4:57Best Practices
- 6:12Secure Design
- 9:41Thread Modeling Tool
- 14:31Secrets
- 16:06GitHub
- 19:01Security Intelligence
- 21:44Developer Security
- 25:12Powershell Toolkit
- 28:56White Source Bolt
- 33:04SonarQube
- 35:01Deployments
- 36:17Azure Defender
- 38:34GitHub Security
- 41:06Dynamic Testing Tools
related talks
30mThe Fifth Element : Azure Secure Devops
01h 10mThe Fifth Element : Azure Secure Devops
52mImplement DevSecOps in Azure
25mSecuring Your DevOps Transformation
55mWhat you need to know about security for cloud DevOps
44mAzure DevSecOps
56mEnter the Matrix: Securing Azure’s Assets
27mMulti Security Checkpoints on DevOps Platform