Container as a Service Security
What You'll Learn
You'll understand how security responsibilities are divided between you and your cloud provider when using managed container services like AWS ECS, Azure AKS, and Google GKE.
The Shared Responsibility Model for CaaS
Container as a Service (CaaS) sits between PaaS and IaaS—you get managed orchestration infrastructure, but you're responsible for securing your containers and workloads.
The Analogy
Think of CaaS like renting a secure apartment building with a managed concierge and maintenance staff. The landlord secures the building, elevators, and utilities (the orchestration platform), but you must lock your own apartment door and protect what's inside (your containers and data).
What the Provider Secures
Your cloud provider manages:
- Control plane security (API servers, schedulers, controllers)
- Node infrastructure (host OS patching, kernel hardening)
- Network foundation (VPC, load balancers, underlying network)
- Physical security and hardware maintenance
- Platform updates and availability
What You Must Secure
You own:
- Container images and their vulnerabilities (scanning, patching)
- Application code and dependencies
- RBAC policies and access controls
- Network policies for pod-to-pod traffic
- Secrets management (how you store/access credentials)
- Runtime security configurations (security contexts, policies)
- Workload identity and service account permissions
- Data encryption (in-transit within cluster, at-rest)
The Gray Zone
Some responsibilities are shared:
- Logging and monitoring: Provider offers tools; you configure and review
- Compliance: Provider certifies platform; you configure compliant workloads
- Network segmentation: Provider enables features; you implement policies
Key Takeaway: In CaaS, the provider secures the orchestration platform, but you're fully responsible for everything running inside your containers—images, code, policies, and runtime configurations.