Pod Security
Also called Pod security standards.
Constraints that limit the privileges and host access a pod may request.
What it is
A set of admission-time constraints that restrict dangerous pod settings such as privilege escalation, host namespace sharing, and sensitive mounts. Enforcing baseline or restricted profiles keeps risky configurations out of the cluster.
Why it matters
Pod-level guardrails are a primary defense against container escape, so their presence or absence often explains how far an attacker could push after landing in a single pod.
In practice
A responder confirms the cluster's missing pod restrictions allowed the attacker to schedule a privileged pod and break out to the node.
What to look for
- Pods running as root or allowing privilege escalation.
- Namespaces without an enforced pod security level.
- Host path, host network or added capabilities in pod specs.
Common mistake
Setting policy to audit and never moving to enforce. Audit mode only reports; it does not block.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Trivy Open source
Scans images, file systems and code for known vulnerabilities and secrets.
-
Falco Open source
Detects suspicious behavior inside running containers and Kubernetes.
-
Sigstore Open source
Signs and verifies software artifacts so you can prove where a build came from.
-
CrowdStrike Falcon Cloud Security Commercial
Protects cloud workloads and containers, from build to runtime.
Read next
- Privileged Container: A container run with host-level capabilities that erase most isolation.
- Container Escape: Breaking out of a container's isolation to reach the host or other workloads.
- Kubernetes RBAC: Role-based authorization governing what identities can do in a cluster.