All 6 domains
26 official competencies
76–102 hrs suggested study
-
Domain 01
15%
Worth 15% of the CKS score, this domain covers the security baseline you lay down before workloads arrive: default-deny NetworkPolicies, CIS benchmark remediation, TLS on Ingress, blocking node metadata and kubelet endpoints, and checking platform binaries against published checksums.
Inside this domain
- Use Network security policies to restrict cluster level access
- Use CIS benchmark to review the security configuration of Kubernetes components (etcd, kubelet, kubedns, kubeapi)
- Properly set up Ingress with TLS
- Protect node metadata and endpoints
- and 1 more competencies
Watch for Policy that allows too much
- Competencies
- 5
Read the domain guide →
-
Domain 02
15%
Cluster Hardening, 15% of the CKS, is about who and what can talk to the Kubernetes API: trimming RBAC grants, limiting service account tokens, closing anonymous or overly broad API access, and upgrading clusters to pick up security fixes.
Inside this domain
- Use Role Based Access Controls to minimize exposure
- Exercise caution in using service accounts e.g. disable defaults, minimize permissions on newly created ones
- Restrict access to Kubernetes API
- Upgrade Kubernetes to avoid vulnerabilities
Watch for Over-removal
- Competencies
- 4
Read the domain guide →
-
Domain 03
10%
The smallest CKS domain at 10%, System Hardening moves below Kubernetes to the node: removing unneeded packages and services, tightening user and cloud identities, closing exposed ports, and confining containers with AppArmor and seccomp.
Inside this domain
- Minimize host OS footprint (reduce attack surface)
- Using least-privilege identity and access management
- Minimize external access to the network
- Appropriately use kernel hardening tools such as AppArmor, seccomp
Watch for Profile name mismatch
- Competencies
- 4
Read the domain guide →
-
Domain 04
20%
Tied for the largest CKS weight at 20%, this domain protects workloads themselves: enforcing Pod Security Standards, encrypting and handling Secrets correctly, isolating tenants and untrusted code with sandboxed runtimes, and encrypting traffic between Pods.
Inside this domain
- Use appropriate pod security standards
- Manage Kubernetes secrets
- Understand and implement isolation techniques (multi-tenancy, sandboxed containers, etc.)
- Implement Pod-to-Pod encryption (Cilium, Istio)
Watch for Invisible rejection
- Competencies
- 4
Read the domain guide →
-
Domain 05
20%
One of three 20% CKS domains, Supply Chain Security covers what you deploy before it runs: building small images, generating and reading SBOMs, restricting registries and verifying signatures at admission, and scanning manifests and images for weaknesses.
Inside this domain
- Minimize base image footprint
- Understand your supply chain (e.g. SBOM, CI/CD, artifact repositories)
- Secure your supply chain (permitted registries, sign and validate artifacts, etc.)
- Perform static analysis of user workloads and container images (e.g. Kubesec, KubeLinter)
Watch for Fail-open admission
- Competencies
- 4
Read the domain guide →
-
Domain 06
20%
The third 20% CKS domain covers what happens after deployment: detecting suspicious behaviour with Falco, tracing an attack to the responsible Pod, keeping containers immutable while they run, and configuring audit logs that record API access.
Inside this domain
- Perform behavioral analytics to detect malicious activities
- Detect threats within physical infrastructure, apps, networks, data, users and workloads
- Investigate and identify phases of attack and bad actors within the environment
- Ensure immutability of containers at runtime
- and 1 more competencies
Watch for Recreated attacker Pod
- Competencies
- 5
Read the domain guide →
Domain names, weights and competencies come from CNCF / The Linux Foundation's official outline (CNCF CKS Curriculum (PDF v1.34, unchanged on the Linux Foundation exam page); exam environment Kubernetes v1.35 as of October 2026). Question counts and study hours are editorial planning estimates, not official figures. Last reviewed October 2026.