
KCSA (Kubernetes and Cloud Native Security Associate) is the Linux Foundation and CNCF's entry-level Kubernetes security certification. It checks that you understand how a cluster is secured: the 4Cs of cloud native security, how each control-plane and node component is protected, Pod Security Standards, RBAC, Secrets, network policies, the Kubernetes threat model, supply chain security and compliance frameworks. It is a multiple-choice exam, so it tests understanding rather than live cluster work. It suits freshers, DevOps engineers and security analysts moving into containers.
This guide follows the official Linux Foundation exam page: the six domains with weights, the security controls you must know, a 4-week plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, multiple choice |
| Duration | 90 minutes |
| Price | US$250 exam only; US$495 with an annual training subscription |
| Prerequisites | None |
| Validity | 2 years |
| Exam eligibility | 12 months from purchase to schedule and take the exam |
| Retakes | A retake is included; check the current terms on the official page |
Read the official KCSA exam page and the candidate handbook before booking. Linux Foundation runs frequent discounts, so compare prices before you pay.
Domains and weights
| Domain | Weight | Sub-topics (from the Linux Foundation) |
|---|---|---|
| Kubernetes Cluster Component Security | 22% | API server, controller manager, scheduler, kubelet, container runtime, kube-proxy, Pod, etcd, container networking, client security, storage |
| Kubernetes Security Fundamentals | 22% | Pod Security Standards, Pod Security Admission, authentication, authorisation, Secrets, isolation and segmentation, audit logging, network policy |
| Kubernetes Threat Model | 16% | Trust boundaries and data flow, persistence, denial of service, malicious code in containers, attacker on the network, access to sensitive data, privilege escalation |
| Platform Security | 16% | Supply chain security, image repository, observability, service mesh, PKI, connectivity, admission control |
| Overview of Cloud Native Security | 14% | The 4Cs, cloud provider and infrastructure security, controls and frameworks, isolation techniques, artefact repository and image security, workload and application code security |
| Compliance and Security Frameworks | 10% | Compliance frameworks, threat modelling frameworks, supply chain compliance, automation and tooling |
The 4Cs of cloud native security
Each layer depends on the one outside it: Cloud (or data centre) → Cluster → Container → Code. A secure container doesn't help if the cloud account is open, so exam questions often ask which layer a control belongs to.
Controls you must know
| Risk | Kubernetes control |
|---|---|
| Anyone who reaches the API server can change the cluster | Authentication (certificates, OIDC), RBAC authorisation, private API endpoint, admission control |
| etcd holds every Secret | Encryption at rest, TLS between API server and etcd, restricted network access, backups |
| Pods run as root or privileged | Pod Security Standards (Privileged, Baseline, Restricted) enforced by Pod Security Admission per namespace |
| Any pod can talk to any pod | NetworkPolicy with default deny (needs a CNI plugin that enforces it) |
| Kubelet API abused | Disable anonymous auth, use Webhook authorisation, keep the read-only port off |
| Untrusted or tampered images | Private registry, image scanning, signing and verification (for example Sigstore cosign), SBOMs, admission policies |
| No record of who did what | API server audit logging with an audit policy |
| Plain-text traffic between services | Service mesh with mutual TLS |
# Enforce the Restricted Pod Security Standard on a namespace
kubectl label namespace payments \
pod-security.kubernetes.io/enforce=restricted \
pod-security.kubernetes.io/warn=restricted
# Default-deny all ingress traffic in the namespace
cat <<'EOF' | kubectl apply -f -
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny-ingress
namespace: payments
spec:
podSelector: {}
policyTypes: ["Ingress"]
EOF
# Check what a service account is allowed to do
kubectl auth can-i --list --as=system:serviceaccount:payments:api
4-week study plan
| Week | Focus | Lab (kind, minikube or k3d on your laptop) |
|---|---|---|
| 1 | 4Cs, cluster components and how each is secured; etcd, kubelet, API server flags | Inspect the API server and kubelet configuration in a kind cluster |
| 2 | RBAC, service accounts, Secrets, Pod Security Standards, network policies, audit logging | Create a least-privilege Role; enforce Restricted on a namespace; add default deny |
| 3 | Threat model: trust boundaries, privilege escalation, container escape, DoS; supply chain, registries, admission control, service mesh | Scan an image with Trivy; sign and verify it with cosign |
| 4 | Compliance frameworks (CIS Kubernetes Benchmark, NIST), threat-modelling frameworks (STRIDE, MITRE ATT&CK for containers), tooling; mocks | Run kube-bench against your lab cluster; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. Name the 4Cs of cloud native security from outermost to innermost.
Cloud, Cluster, Container, Code.
2. Which component stores all cluster state, including Secrets?
etcd.
3. By default, how are Kubernetes Secrets stored in etcd?
Base64-encoded, not encrypted, unless encryption at rest is configured.
4. Which Pod Security Standard is the most restrictive?
Restricted.
5. Which built-in admission controller enforces Pod Security Standards per namespace?
Pod Security Admission.
6. You create a NetworkPolicy but traffic still flows. What is the likely reason?
The cluster's CNI plugin doesn't enforce network policies.
7. Which RBAC object grants permissions across all namespaces?
A ClusterRole bound with a ClusterRoleBinding.
8. A pod mounts the host's root filesystem and runs privileged. Which threat does this enable?
Container escape and privilege escalation to the node.
9. Where do you find a record of who deleted a deployment?
The API server audit log.
10. How can you make sure only images signed by your team are deployed?
Sign images (for example with cosign) and verify signatures with an admission policy.
11. What does an SBOM help with?
Knowing exactly which components and versions are in an image, so you can find affected images when a new CVE appears.
12. What gives encrypted, mutually authenticated traffic between services without changing app code?
A service mesh with mutual TLS.
13. One pod uses all the node's CPU and starves others. Which threat is this, and what limits it?
Denial of service; resource requests and limits, plus ResourceQuota and LimitRange.
14. Which widely used benchmark gives configuration checks for Kubernetes clusters?
The CIS Kubernetes Benchmark (kube-bench automates it).
15. Should application pods use the default service account token if they never call the API?
No. Set automountServiceAccountToken: false and give each workload its own least-privilege service account.
After KCSA
- Start with KCNA if Kubernetes is new to you, and add hands-on skills with CKAD and the CKA and CKS roadmap.
- Learn Kubernetes in depth on our Kubernetes course and DevSecOps course.
- See live DevOps and security jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches Docker, Kubernetes, DevSecOps and cloud security with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the KCSA exam?
The Linux Foundation and CNCF's Kubernetes and Cloud Native Security Associate exam: an online, proctored, multiple-choice exam on Kubernetes security fundamentals.
How long is the KCSA exam?
90 minutes.
Does KCSA have prerequisites?
No. There are no prerequisites.
How long is KCSA valid?
2 years.
Which KCSA domains have the most weight?
Kubernetes Cluster Component Security and Kubernetes Security Fundamentals, at 22% each.
Is KCSA hands-on like CKS?
No. KCSA is multiple choice; CKS is a performance-based exam on a live cluster.



