Cloud’s Dirty Little Secret: It Was Misconfigs All Along
summary
Most cloud breaches trace to misconfigurations, not exotic exploits: hundreds of Azure reviews show recurring failures like public storage buckets, legacy key‑based auth and exposed Kubernetes dashboards, plus permission sprawl and many unused service principals (example: an admin last used 192 days ago). Remediations that work include infra‑as‑code linting (TFsec, Checkov), policy‑as‑code (Azure Policies, Microsoft Cloud Security Benchmark) and runtime detection (Falco); example gap: Azure AI has 35 baseline controls but only 4 built‑in policies.
AI-written summary · about
chapters (10)
- 0:00Cloud misconfigurations
- 1:29Introduction
- 2:54Misconfigurations top breaches
- 8:52Four horsemen of misconfig
- 15:14Overprovisioned permissions
- 28:46Security via policies
- 38:37Azure security benchmark
- 45:21Tools for cloud security
- 53:05Key takeaways
- 55:38Q&A
related talks
45mProtecting you from you: Misconfiguration-caused breaches
26mCloud Security Lessons
40mWork Smarter Not Harder: Tips to Approach Cloud Security the Easier Way
52mUncovering Azure's Silent Threats: A Journey Into Cloud Vulnerabilities
41mUncovering Azure's Silent Threats: A Journey into Cloud Vulnerabilities
44mDeveloper Productivity Shouldn’t Breach Security
36mCloud Hacking Scenarios
25mSecuring Your DevOps Transformation