The Linux Foundation CKS exam preparation guide is designed to provide candidates with necessary information about the Kubernetes Security Specialist exam. It includes exam summary, sample questions, practice test, objectives and ways to interpret the exam objectives to enable candidates to assess the types of questions-answers that may be asked during the Certified Kubernetes Security Specialist (CKS) exam.
It is recommended for all the candidates to refer the CKS objectives and sample questions provided in this preparation guide. The Linux Foundation Kubernetes Security Specialist certification is mainly targeted to the candidates who want to build their career in Cloud & Containers domain and demonstrate their expertise. We suggest you to use practice exam listed in this cert guide to get used to with exam environment and identify the knowledge areas where you need more work prior to taking the actual Certified Kubernetes Security Specialist exam.
Linux Foundation CKS Exam Summary:
| Exam Name | Certified Kubernetes Security Specialist |
| Exam Code | CKS |
| Exam Price | $395 USD |
| Duration | 120 minutes |
| Number of Questions | 15-20 |
| Passing Score | 67% |
| Recommended Training / Books | Kubernetes Security Essentials (LFS260) |
| Schedule Exam | The Linux Foundation Training & Certification |
| Sample Questions | Linux Foundation CKS Sample Questions |
| Recommended Practice | Certified Kubernetes Security Specialist (CKS) Practice Test |
Linux Foundation Kubernetes Security Specialist Syllabus:
| Section | Objectives | Weight |
|---|---|---|
| Cluster Setup |
- 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 objects with security control - Protect node metadata and endpoints - Minimize use of, and access to, GUI elements - Verify platform binaries before deploying |
10% |
| Cluster Hardening |
- Restrict access to Kubernetes API - Use Role Based Access Controls to minimize exposure - Exercise caution in using service accounts e.g. disable defaults, minimize permissions on newly created ones - Update Kubernetes frequently |
15% |
| System Hardening |
- Minimize host OS footprint (reduce attack surface) - Minimize IAM roles - Minimize external access to the network - Appropriately use kernel hardening tools such as AppArmor, seccomp |
15% |
| Minimize Microservice Vulnerabilities |
- Setup appropriate OS level security domains - Manage Kubernetes secrets - Use container runtime sandboxes in multi-tenant environments (e.g. gvisor, kata containers) - Implement pod to pod encryption by use of mTLS |
20% |
| Supply Chain Security |
- Minimize base image footprint - Secure your supply chain: whitelist allowed registries, sign and validate images - Use static analysis of user workloads (e.g.Kubernetes resources, Docker files) - Scan images for known vulnerabilities |
20% |
| Monitoring, Logging and Runtime Security |
- Perform behavioral analytics of syscall process and file activities at the host and container level to detect malicious activities - Detect threats within physical infrastructure, apps, networks, data, users and workloads - Detect all phases of attack regardless where it occurs and how it spreads - Perform deep analytical investigation and identification of bad actors within environment - Ensure immutability of containers at runtime - Use Audit Logs to monitor access |
20% |