KCNA ยท Kubernetes security
What are the 4Cs of cloud native security?
Cloud, Cluster, Container, Code layers and what protects each.
Key points
- Four nested layers: Cloud (infrastructure, provider account, network), Cluster (API access, RBAC, network policies, encryption), Container (image contents, runtime privileges, limits) and Code (application logic, dependencies, secrets handling).
- Each layer builds on the one outside it, so a weak outer layer cannot be fixed from the inside.
Source: https://kubernetes.io/docs/concepts/security/cloud-native-security/
Practice questions
In the 4Cs model, which layer is the outermost one?
- Code
- Container
- Cloud
- Cluster
Show answer
Answer: C. Cloud
Cloud (or the data center/infrastructure) is the outer layer; Cluster, Container and Code sit inside it in that order.
Which measures belong to the Cluster layer?
- Scanning images for known vulnerabilities
- RBAC rules limiting API access
- Reviewing third-party library versions
- Network policies between Pods
- Hardening the VM firewall at the provider
Show answer
Answer: B. RBAC rules limiting API access, D. Network policies between Pods
RBAC, network policies and API server TLS protect the cluster itself. Image scanning is a Container concern and dependency review is a Code concern.
True or false: if the application code is secure, the outer layers (Cluster, Cloud) matter much less.
Show answer
Answer: False
False. Each layer depends on the ones outside it; a compromised node or exposed API can bypass perfectly secure code.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
