Verifiable Build Environments in the Cloud: Powered by Sigstore and Enclaves
summary
Architecture that combines Sigstore signatures with CPU attestation to keep signing keys off‑host and verifiably bind build inputs to outputs, using AMD SEV‑SNP confidential VMs for lift‑and‑shift and enclaves for minimal TCB where code is recompiled. A trusted build service orchestrates GitHub Actions style runners, records firmware and boot hashes into provenance records, and publishes attestations so builds can be verified later — demo shows an end‑to‑end cloud build and signature flow.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:21OPEN-SOURCE TOOLS
- 2:30CHALLENGES TO ADOPT SAAS CI/CD
- 4:20INTEL SGX SOFTWARE GUARD EXTENSION
- 6:23CONFIDENTIAL VMS (AMD SEV-SMP)
- 9:44OVERVIEW
- 12:24TRIGGER A BUILD-VERIFY BUILD SYSTEM INTEGRITY
- 14:49ADVANTAGES
- 15:27RECAP
related talks
18mYou Can Sign It, But Can You Trust It? Securing the Compilation Process
39mAuthenticating Supply-chain Metadata: Building Remote Code Attestations on GitHub
46mEnhancing Artifact Security with GitHub’s Build Provenance...
30mHow Secure Is Your Build/Server?
50mZero-Trust Supply Chain Security with Sigstore, TektonCD and SPIFFE
33mGrowing the Chain: Trusting Build Provenance from Userspace
54mFrom "Trust Me" to "Verify Me"
25mProving Trust: Signed Supply Chains and Verifiable Deployments at the Edge