Walking on Broken Clouds
summary
Cloud security programs start by answering what accounts exist, who technically owns them and who has budget authority, then trim CSPM noise by adopting company-specific cloud standards and feeding CloudTrail into the SOC and Splunk for investigations. Turning on provider tools like GuardDuty, Macie and IAM Access Analyzer yields quick wins; tagging, blanket service control policies and naive auto remediation fail culturally and technically; treat developers as the primary control and automate checks in pipelines.
AI-written summary · about
chapters (20)
- 0:00Start
- 7:04Immediate tasks
- 10:10Global Haystack
- 13:31What the heck is the cloud anyway?
- 14:13Custom Cloud Standards
- 18:27Inventory
- 19:23Centralized Cloud Team
- 20:39Cloud Provider Tooling
- 23:33Pitfalls of prevention
- 25:19Tagging
- 27:50The allure of auto-remediation
- 28:57Farris's Three Laws
- 29:33The pipeline excuse
- 31:13Having a Cloud Security Team
- 32:06Policy requirements to appease others
- 33:05CSPM is a tarpit
- 35:04My journey of self awareness
- 36:40Developers are the key
- 37:13Part of a complete breakfast...
- 41:31RSAConference 2023
related talks
51mCloudSec Hero to Zero: Self-Obsolescing Through Prolific Efficiency
50mArchitecting a secure cloud framework
47m3 steps to help mitigate cloud risks
58mCloud Attack Surface Management
31mSeeing Through the Fog - Navigating the Security Landscape of a Cloud-First World
15mHelping security and developers to understand one another
31mA Comprehensive Approach to Cloud Security Posture Management
18mManaging your cloud security universe as one