So we're all just trusting these new "enclave" artifacts now? Fine. Here's our policy for approving changes to the images they build. It's from our internal wiki. Probably seems draconian.
Every change requires three senior staff who've logged into the physical build server in the last month to sign off. No AI-generated patches. Full diff of the Dockerfile and any binaries in the final layer. If it touches the entrypoint or attestation logic, we re-key everything from scratch. Old ways worked. This is just a fancy chroot.
Okay but I'm new to this - what's the actual threat you're stopping here? Is it that someone pushes a bad image, or that the build server itself gets owned?
The three senior staff rule is interesting. What if two are on vacation and there's a critical security patch? Do you just... wait?