This syllabus tracks the official CKS curriculum. CKS is a security specialization, not a starting point — it assumes you hold an active CKA certification and can already install, operate, and troubleshoot a cluster. You start with a short foundation refresher, then work through the six weighted security domains, each linking to a hands-on tutorial you can repeat on your own VMs.
Open Before You Begin first if your lab is not ready. The walkthroughs use a multi-node kubeadm cluster with one control-plane node and two workers, and several lessons install extra tools — kube-bench, Trivy, Cosign, Falco, Cilium, Istio, and gVisor — that you tear down afterward. The chapters follow a learning path from cluster setup through supply chain to runtime security, not the accordion order on the Linux Foundation marketing page.
Foundation topics such as RBAC, ServiceAccounts, and Secrets are shared with the CKA and CKAD courses; on the CKS hub they carry the extra security angle the exam expects. For topics outside the CKS blueprint, browse the wider Kubernetes tutorial.
What the CKS exam expects
The competency bullets below come from the current CKS blueprint, grouped by exam weight. CKS is a two-hour, performance-based exam run on Kubernetes v1.35 — every task is hands-on work on a live cluster.
Cluster Setup (15%)
- 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
- Verify platform binaries before deploying
Cluster Hardening (15%)
- 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
System Hardening (10%)
- Minimize host OS footprint (reduce attack surface)
- Use least-privilege identity and access management
- Minimize external access to the network
- Appropriately use kernel hardening tools such as AppArmor, seccomp
Minimize Microservice Vulnerabilities (20%)
- 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)
Supply Chain Security (20%)
- 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)
Monitoring, Logging and Runtime Security (20%)
- 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
- Use Kubernetes audit logs to monitor access
The three heaviest domains — Minimize Microservice Vulnerabilities, Supply Chain Security, and Runtime Security — together account for 60% of the exam, so weight your practice toward Pod Security Standards, image scanning and signing, and Falco. Cluster Setup and System Hardening are smaller but reward knowing the exact command syntax cold.
Use Start the course to open Before You Begin, or jump straight to any competency in the syllabus.

