Top 18 Azure security fails and how to avoid them
summary
Assessment of over 100 Azure deployments finds 18 common pitfalls and a scanned enterprise (≈10 subscriptions, ~200 resources) where storage misconfigurations are the top issue. Shows exact failures: storage accounts without HTTPS or at-rest encryption, service principals created as subscription owners, activity logs retained only 90 days by default. Demonstrates fixes: run the Azure Security Kit scanner, restrict scopes and use PIM, store and rotate secrets in Key Vault, enable App Insights/ATP, use NSGs, JIT, WAF and API gateway.
AI-written summary · about
chapters (17)
- 0:00Intro
- 3:04What to expect in this session
- 3:39With great power comes great responsibility
- 7:18Security controls for Azure applications
- 9:18Cloud security: reality check
- 16:00Role-Based Access Control
- 18:46Privileged Identity Management
- 21:17STRIDE
- 23:30Security fail #1
- 29:40Security fail #2
- 31:45Security fail #3
- 33:48Security fail #4
- 38:46Security fail #5
- 42:29Security fail #6
- 47:49Security fail #7
- 48:41Secure DevOps kit for Azure (AzSK)
- 50:12Materials
related talks
39mTop 13 best security practices for Azure
20mThe 10 Most Common Azure Mistakes (And How To Fix Them)
22mAzure Infrastructure - What Not to Do
57mCloud’s Dirty Little Secret: It Was Misconfigs All Along
49mTop 5 ways to secure Azure resources
49mAzure DevOps security - Lessons learned
52mUncovering Azure's Silent Threats: A Journey Into Cloud Vulnerabilities
55mWhat you need to know about security for cloud DevOps