Don't Destroy Your Datacenter with Azure DevOps
summary
Azure DevOps often ships without Azure AD auditing enabled so connect the org to Azure Active Directory, turn on log audit events (default retention 90 days) and stream to a SIEM for long term alerting. Use branch lock main branch plus branch policies and require approvers. Create service connections constrained to resource group scope (avoid hidden subscription‑wide grants), prefer the automatic service principal, and audit role/owner assignments and managed identities.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:04Why this talk matters
- 3:31Protect data code infrastructure
- 5:17Know privileged accounts
- 9:09Azure AD security basics
- 13:02Auditing Azure DevOps limits
- 15:07Azure DevOps to Azure AD
- 19:46Branch policies security
- 25:01Azure locks protection
- 26:24Evaluate Azure connections
- 28:14Connection scope dangers
- 31:31Monitor connection changes
- 33:56Organizational risks
- 34:41Setup recommendations
- 37:28Summary
- 37:48Q&A
related talks
46mLet Azure control your DevOps Pipelines
42mAzure DevOps security - Lessons learned
52mImplement DevSecOps in Azure
34mDevOps from an Auditor’s Perspective: A Meaningful Partnership to Drive Business Transformation
56mSecuring organizations pipelines and integrations in Azure DevOps Q&A
01h 05mCreating Azure SQL Database Users Programmatically using Azure DevOps
01h 03mA lap around Azure Devops
25mSecuring Your DevOps Transformation
