The Hacker's Guide to Cloud Governance
summary
Claim: most cloud breaches trace to failed governance and identity, not broken tech. Shows a working approach: build a Cloud Center of Excellence, maintain an account registry, write SMART control objectives, then map vendor-specific control specifications (he demos scraping Azure/CIS docs into a database with simple code and ChatGPT help). Recommends SSO federation, centralizing GuardDuty/Azure Defender feeds, service control policies, org isolation, CSPM/CNAPP tooling and automation focused on production blast‑radius.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:06Cloud governance challenges
- 10:06Executive motivations and politics
- 17:42Cloud Center of Excellence
- 23:40Cloud registry and asset tracking
- 27:15Control objectives and frameworks
- 33:13Vendor tools and control specifications
- 37:06Preventative governance controls
- 41:18Tool selection and outcomes
- 43:05Frictionless governance strategies
- 51:20Summary and closing
related talks
48mControlling Clouds: Beyond Safety
26mCloud Security Lessons
57mBest practices for cloud governance at scale
57mCloud’s Dirty Little Secret: It Was Misconfigs All Along
26mHow CISA is approaching authentication and cloud security in the era of great power competition?
45mProtecting you from you: Misconfiguration-caused breaches
31mA Comprehensive Approach to Cloud Security Posture Management
25mSecurity, Identity - Back to the Drawing Board?