Kubernetes Security Specialist (CKS): First Edition

Kubernetes Certified: Security Specialist

About Certified Kubernetes Security Specialist (CKS)

Certified Kubernetes Security Specialist (CKS) is a performance-based certification exam that assesses candidates’ understanding of Kubernetes and cloud security in a realistic, simulated environment. Prior to taking the CKS test, candidates must have passed the Certified Kubernetes Administrator (CKA) certification. CKS can be purchased, but it cannot be scheduled until CKA certification is obtained.

On the day of the CKS exam (including retakes), the CKA certification must be active (not expired).

Who is it for?

A Certified Kubernetes Security Specialist (CKS) is a skilled Kubernetes practitioner (must be CKA certified) who has demonstrated proficiency in a wide range of best practices for protecting container-based applications and Kubernetes platforms during development, deployment, and runtime.

What is demonstrate?

Obtaining a CKS certifies a candidate’s ability to secure container-based applications and Kubernetes platforms during development, deployment, and runtime, and that they are qualified to do so in a professional setting.

The CKS curriculum (areas of study and weight of each area) is as follows at the time of writing:

1. Cluster Setup
2. Cluster Hardening
3. System Hardening
4. Minimize Microservice Vulnerabilities
5. Supply Chain Security
6. Monitoring, Logging and Runtime Security

Recommended Knowledge

1. Use Network security policies to restrict cluster level access
2. Use CIS benchmark to review the security configuration of Kubernetes components (etcd, kubelet, kubedns, kubeapi)
3. Properly set up Ingress objects with security control
4. Protect node metadata and endpoints
5. Minimize use of, and access to, GUI elements
6. Verify platform binaries before deploying
7. Restrict access to Kubernetes API
8. Use Role Based Access Controls to minimize exposure
9. Exercise caution in using service accounts e.g. disable defaults, minimize permissions on newly created ones
10. Update Kubernetes frequently
11. Minimize host OS footprint (reduce attack surface)
12. Minimize IAM roles
13. Minimize external access to the network
14. Appropriately use kernel hardening tools such as AppArmor, seccomp
15. Setup appropriate OS level security domains e.g. using PSP, OPA, security contexts
16. Manage Kubernetes secrets
17. Use container runtime sandboxes in multi-tenant environments (e.g. gvisor, kata containers)
18. Implement pod to pod encryption by use of mTLS
19. Minimize base image footprint
20. Secure your supply chain: whitelist allowed registries, sign and validate images
21. Use static analysis of user workloads (e.g.Kubernetes resources, Docker files)
22. Scan images for known vulnerabilities
23. Perform behavioral analytics of syscall process and file activities at the host and container level to detect malicious activities
24. Detect threats within physical infrastructure, apps, networks, data, users, and workloads
25. Detect all phases of attack regardless where it occurs and how it spreads
26. Perform deep analytical investigation and identification of bad actors within environment
27. Ensure immutability of containers at runtime
28. Use Audit Logs to monitor access

The following general domains and their weights on the exam are included in this exam curriculum: