
The container image you scanned at build time isn't the one running in production. Base images get rebuilt, tags get repointed, and by week three your "clean" deployment is running a different SHA than what passed your scanner.
Admission controllers that verify image digests — not tags — catch this. Pair with signed images (Sigstone/Cosign) and your cluster refuses to run anything you didn't approve.
What's actually running in your cluster right now? cloudsecurityalliance.org/research/publi… #KubernetesSecurity
English