Cloud Isn’t Secure by Default: What Containers Changed About Risk - Seguridad Mania.com - España y América Latina

The shift from monolithic architecture to Kubernetes and managed cloud services has revolutionized delivery, but it has also birthed a dangerous myth: that the cloud is secure by default. While your cloud provider manages the physical hardware, the explosion of containerized complexity has created a massive blind spot in the Shared Responsibility Model. Join Intruder VP Product Andy Hornegold as he dismantles the assumption that outsourcing infrastructure means outsourcing risk. This session dives deep into the reality of modern container security - moving beyond simple vulnerability scanning to true exposure management. Why attend? Traditional security models are failing in the face of containerized environments. Even the architects of Kubernetes admit the system’s end-to-end implications are staggering. We will explore why ‘secure’ code in development can become a critical liability in production, and why the industry’s obsession with CVE counts often misses the mark. What you’ll learn: - The Complexity Gap: How moving to the cloud actually increases your attack surface. - Lessons from the Field: A look at high-profile provider vulnerabilities (like the Microsoft agent flaw) and what they mean for your "secure" assets. - Vulnerabilities vs. Exposure: Why scanning images isn't enough - we’ll discuss how to identify which containers are actually reachable by hackers and why ‘zero CVEs’ is often a distraction from real risk. - The Ownership Paradox: Who really owns container security - DevOps or Security?