KCNA ยท Kubernetes security
What do admission controllers and policy engines do, and how does this relate to the supply chain?
Admission controllers, policy engines (Kyverno, OPA Gatekeeper), image scanning and signing, SBOM concept.
Key points
- Admission controllers run after authentication and authorization and can mutate or reject objects before they are stored.
- Validating and mutating webhooks let external policy engines (Kyverno, OPA Gatekeeper) decide, e.g. only trusted-registry images.
- Image scanning: finds known vulnerabilities.
- Image signing (e.g. Sigstore cosign): verifiable provenance.
- SBOM: list of components inside an artifact.
Source: https://kubernetes.io/docs/concepts/security/controlling-access/
Practice questions
Where in the API request flow do admission controllers run?
- Before authentication
- After authorization, before the object is stored
- Only after the Pod is running on a node
- Inside the container runtime
Show answer
Answer: B. After authorization, before the object is stored
Admission control comes after authentication and authorization and before the object is persisted.
Which tools or concepts are policy engines or controls used at admission time?
- Kyverno
- etcd
- OPA Gatekeeper
- CoreDNS
- Pod Security Admission
Show answer
Answer: A. Kyverno, C. OPA Gatekeeper, E. Pod Security Admission
Kyverno and OPA Gatekeeper are policy engines that plug into admission. Pod Security Admission is a built-in admission controller. etcd and CoreDNS serve other roles.
True or false: an SBOM is a signature that proves who built an image.
Show answer
Answer: False
False. An SBOM is an inventory of the components and dependencies inside software. A signature, for example made with cosign, is what proves provenance.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
