Cloud security explained: What’s left exposed?

The article clarifies AWS’s Shared Responsibility Model, emphasizing that customers must secure application, identity, OS, network, and configuration layers, with examples like SSRF to the metadata service, public S3 bucket misconfigurations, IDOR risks in SaaS apps, and the need for patch management and proper network exposure; it recommends defenses such as fixing SSRF, enabling IMDSv2, enforcing least privilege and secure access patterns, and keeping runtimes up to date, and concludes by promoting Intruder’s agentless cloud security scanning to detect misconfigurations, vulnerabilities, and exposed services.