Cloud Security
Secure cloud environments across AWS, Azure, and GCP including IAM, container security, and serverless.
10 Topics
Key concepts
3 Levels
Beginner to Advanced
5 Tools
Curated for this track
8 Questions
Test yourself
About this track
The perimeter is an IAM policy now.
Cloud platforms rearranged the security model: the network perimeter thinned out and identity became the real control plane. Most cloud breaches are not exotic — they are a public storage bucket, an over-permissive role, or a leaked key with no expiry.
This track covers the three major providers with an emphasis on what transfers between them, then goes deep on identity and access management, container and Kubernetes security, and the misconfiguration classes that dominate real incidents.
It assumes some infrastructure background. If you have not done the Network Security track, start there.
Key topics
10 topics grouped into three modules, in the order you should meet them.
- 01
Provider foundations
4 topics- 1.
AWS Security
IAM, S3, VPC, and CloudTrail — the four services behind most AWS incidents.
- 2.
Azure Security
Entra ID, role assignments, and the hybrid identity surface joining cloud to on-premises.
- 3.
GCP Security
Projects, service accounts, and the organisation policy hierarchy.
- 4.
IAM & Access Control
Least privilege, role assumption, and the privilege-escalation paths policies create.
- 1.
- 02
Identity & workloads
4 topics- 5.
Container Security
Image provenance, registry scanning, and shrinking the runtime attack surface.
- 6.
Kubernetes Security
RBAC, network policies, admission control, and pod security standards.
- 7.
Serverless Security
Function permissions, event injection, and dependency risk without a host to patch.
- 8.
Cloud Misconfigurations
Public buckets and wildcard policies — the leading cause of real cloud breaches.
- 5.
- 03
Posture & compliance
2 topics- 9.
Cloud Compliance
Mapping controls to CIS benchmarks and the shared responsibility model.
- 10.
Multi-Cloud Security
Consistent policy and identity federation across providers that disagree on everything.
- 9.
What you'll be able to do
- Audit an AWS, Azure, or GCP account for the misconfigurations that matter most
- Design least-privilege IAM policies and explain the blast radius of each role
- Secure a container build pipeline and a Kubernetes cluster's runtime posture
- Map a cloud environment's attack paths from an initial credential outward