Lesson 229
Cloud & Container Security
shared responsibility · misconfigurations · container isolation · Kubernetes
1:00How cloud shared responsibility, IAM least privilege, secrets management, container isolation, image hardening, and Kubernetes network policies combine into a layered defense.
By the end, you can
- Explain the shared responsibility model and identify which security items always belong to the customer.
- Classify a given cloud setup by service model (IaaS/PaaS/SaaS) and state the customer's security obligations in each.
- Name the four most common customer-side cloud misconfigurations and the control that mitigates each.
- Trace the Capital One 2019 breach chain and identify where least-privilege IAM would have stopped it.
- Distinguish container isolation from VM isolation and explain why a shared kernel widens the blast radius of a kernel exploit.
- Identify the three Linux mechanisms (namespaces, cgroups, capabilities/seccomp) and state the isolation question each answers.
- List the key practices in a hardened Dockerfile (minimal base, digest pin, non-root, CVE scanning).
- Describe the Kubernetes default-deny NetworkPolicy pattern and explain why the default flat network is dangerous.
- Explain why Kubernetes Secrets stored as base64 are not confidential and state two controls that actually protect them.
- Apply the 4 C's model to evaluate the security of a cloud-native system layer by layer.
Up next in Graphics, DevOps & Cloud Systems




