Moving to the cloud does not move the responsibility for security with it. Most cloud breaches come from mistakes in how customers configure their own accounts, not from flaws in the provider. You'll start with the shared responsibility model to see who secures what across IaaS, PaaS and SaaS, then look at the misconfigurations that cause real incidents, such as public storage buckets, overly permissive IAM policies and exposed management ports.
Next, you'll turn to containers. You'll learn how to build secure Docker images with minimal bases, non-root users, SBOMs and no embedded secrets, and how to find problems early by scanning images and configuration files with Trivy. The module finishes with Kubernetes security: RBAC, network policies, pod security, secrets handling and layered defence.
Once your cloud and container workloads are hardened, you'll be ready for the next module, Threat Detection & Incident Response, where you spot attacks and respond when something gets through.
What the cloud provider secures versus what you must secure, how that changes across IaaS, PaaS and SaaS, and how AWS and Azure compare.
The most common causes of cloud breaches, including public S3 buckets, overly permissive IAM policies and exposed SSH or RDP, with a cloud security checklist for AWS and Azure.
13 practical ways to shrink the attack surface of container images: lean and immutable builds, non-root users, SBOMs, provenance, keeping secrets out and host hardening.
A hands-on Trivy walkthrough: scanning a Docker image, patching critical and high vulnerabilities, checking for misconfigurations, and deciding what to do with lower risks.
Whether Kubernetes is secure by default, plus RBAC, network policies, pod security, secrets management, API server risks and a layered model across the control plane, nodes and containers.