07-25, 15:00–15:20 (US/Eastern), Room 2/3
Isolated, ephemeral builders are table stakes for a secure build system, which is why people are turning to cloud CI/CD solutions like Tekton, GCP Cloud Build, or GitHub Actions. Moving your build to the cloud isn't all roses though, as existing build processes often rely on access to infrastructure on prem or in another cloud provider. In the past year, cloud CI/CD systems have added OIDC as a way to provide that access. This is quite different than an end-user OAuth2 flow, so we'll go over what it looks like, common security pitfalls, and how to avoid them. We'll then take it a step further, and show how the open source sigstore project can use OIDC to attest to the build process, and even sign your builds without managing a private key.
Zach is a staff security engineer at GitHub, where he works on cloud security and container security internally, as well as open source security externally. He enjoys time away from the computer biking and homesteading.