A team sets network ACLs outside the cluster, in front of the Kubernetes API endpoint, so that only the administrators' IP ranges can reach it. In the 4Cs model, which layer does this control belong to?
Choose one.
The 4Cs are Cloud (or corporate data centre / co-location), Cluster, Container and Code; the Cloud layer is the infrastructure the cluster runs on.
The control is a network rule set in the infrastructure the cluster runs on, outside Kubernetes, so it sits in the outermost layer, Cloud. The Kubernetes guidance on infrastructure security names 'network access to the API server' as a Cloud-layer item: the control plane should not be publicly reachable and should be limited by network ACLs to the addresses that administer it. It is tempting to call it Cluster because it protects the API server, but Cluster-layer controls are the ones configured through Kubernetes itself.
- Ask where the control is configured: in the provider's infrastructure or inside Kubernetes.
- A network ACL set outside the cluster is infrastructure, so it is a Cloud-layer control.
- Reserve Cluster for Kubernetes-native settings such as RBAC and NetworkPolicy.
Exam tip: Configured in the infrastructure outside Kubernetes = Cloud layer, even when it protects a Kubernetes component.
KCSA: The 4Cs of Cloud Native Security, Infrastructure Security and Security Controls — the lesson that teaches this.