Episode 75 — Secure Cloud Architectures: Shared Responsibility and Common Misconfiguration Traps

This episode explains cloud security as an architecture and governance challenge built on shared responsibility, a concept that GSEC often tests by asking who is responsible for which control in a hosted environment. You’ll connect provider responsibilities, such as underlying physical security and core service availability, to customer responsibilities, such as identity, configuration, data protection, logging, and workload hardening, then show how most cloud incidents stem from simple misconfigurations rather than advanced exploits. We’ll walk through a scenario where a team migrates quickly and accidentally exposes services, over-permissions identities, and disables logging for cost reasons, then translate that into defensive patterns like secure defaults, least privilege IAM, segmented networking, and continuous configuration monitoring. Best practices include defining ownership, using infrastructure-as-code with review gates, maintaining inventories of assets and exposures, and validating that monitoring and incident response workflows work in the cloud context. Troubleshooting focuses on cloud sprawl, inconsistent policy across accounts, and the gap between “service is available” and “service is securely configured and observable.” Produced by BareMetalCyber.com, where you’ll find more cyber audio courses, books, and information to strengthen your educational path. Also, if you want to stay up to date with the latest news, visit DailyCyber.News for a newsletter you can use, and a daily podcast you can commute with.