Cloud Attack Surface Management
summary
Claims that cloud risk comes from the same application exploits applied to infrastructure as code and public APIs, citing the Log4j outbreak and researcher-discovered CSP weaknesses that show multi-tenant isolation breaks (affecting several banks) and an incident where automated patching introduced privilege escalation. Recommends combining app and cloud security, using CSPM/KSPM and runtime protections, enforcing policy-as-code guardrails, prioritizing fixes by impact (one IaC line often remediates thousands of instances), measuring scanning coverage and mean time to redeploy.
AI-written summary · about
chapters (14)
- 0:00Start
- 5:19Definition
- 6:02What is different?
- 7:57Layers of Cloud attack surface
- 10:44Responsibilities for Cloud attack surface management
- 17:50Cloud exploitation techniques examples
- 20:22Attack surface analysis conclusions
- 21:14Protection and prevention
- 22:02Defense in depth
- 24:42Cloud-native attack surface management
- 26:43CISO Programs view on Cloud and AppSec
- 28:54Cloud security remediation life cycle
- 31:19Process for misconfigurations reduction
- 31:52Attack surface management metrics
related talks
50mArchitecting a secure cloud framework
26mCloud Security Lessons
18mManaging your cloud security universe as one
31mUnderstanding Cloud Control Plane Compromise Attacks
15mHelping security and developers to understand one another
56mNavigating the Cloud Native Security Landscape
31mCloud Threat Landscape - 2021
40mCloud Security Novice to Native in 10 Steps: A CNAPP Approach