Kubernetes security fundamentals: Admission Control
ID: a29c69ea-1d47-5ea5-a0e1-e163a1b78525
STIX ID: report--a29c69ea-1d47-5ea5-a0e1-e163a1b78525
Feed Name: Datadog Security Labs
This article explains Kubernetes admission control as the final stage of API request processing, detailing the roles of mutating and validating controllers, default built-ins (e.g., PodSecurity, ServiceAccount), and external webhooks (Validating/MutatingWebhookConfiguration). It outlines key security considerations—such as fail-open vs fail-closed behavior, controller placement, and privilege exposure—and compares policy mechanisms: Pod Security Admission (namespace-level profiles), Validating Admission Policy using CEL (flexible validation), and external controllers like Kyverno and OPA Gatekeeper. The piece emphasizes using admission control to restrict risky pod configurations (e.g., privileged pods) while understanding limitations and operational risks.
Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.
