Lightning Talk: Don't Wait, Secure your DevOps Processes Using Open Standar...
summary
Claim: configure OpenID Connect trust between CI and any secret store so CI emits a JWT that exchanges for short‑lived access tokens, letting pipelines retrieve secrets without vendor lock. Steps: declaratively register the CI as an OIDC client, have GitLab/GitHub/CircleCI mint a JWT, exchange it at the provider, then fetch secrets. Results: short tokens (typical 5‑minute expiry), no vendor integration wait (no vendor lock), tradeoff is initial setup complexity and storage costs.
AI-written summary · about
chapters (5)
related talks
28mSecure CI/CD Using JSON Web Token (JWT)
17mOIDC and CICD: Why Your CI Pipeline Is Your Greatest Security Threat
25mIntegrating Vault with CI/CD pipelines: Best practices and pitfalls
05mBreaking Up with Long-lived Secrets: Secure Automation in the Mode...
20mSecuring OIDC Federation in CI/CD Workflows
34mWho Are You? I Really Want to Know… the Magic Behind OIDC
45mAttackers' Nightmare: An Infrastructure Without Secrets
49mEnhancing CI/CD Secrets Security: The 3Rs Approach