Attacking & Defending Supply Chains. How we got Admin in your Cloud,...
summary
Shows concrete attacks across GitHub Actions, Buildkite and Terraform: a freshly created repo or PR can run pre-merge RCE to memory-dump org secrets and the Actions token, use OIDC federation to assume AWS IAM roles, and even perform a terraform plan apply bypass that creates resources (demo: S3 bucket appeared during a plan). Walks through the exact files and agent/agent-cluster mechanics that make this possible and demonstrates mitigations: GitHub environments, Buildkite clusters, pre-plan checks and GitHub push-rule sets.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:20CI/CD tool architectures
- 7:04Terraform and infrastructure
- 12:48Security vulnerabilities
- 17:39Pre-merge risks
- 25:17Mitigation strategies
- 33:28Future improvements
- 40:50Q&A and closing
related talks
42mProtecting CI/CD from malicious deploys
15mGitHub Actions: a time bomb for supply chain security
42mProtecting Your GitHub from Supply Chain Attacks
57mGitHub Actions: A Cloudy Day for Security
23mBreaking the Build: How Attackers Abuse GitHub Actions
52mGitHub Actions Security: From CI Nightmare to Supply Chain Sentinel
55mBeyond the Commit: Weaponizing and Hardening GitHub Actions
55mGitHub Actions: Vulnerabilities, Attacks, And Counter-Measures