Least-Privilege Boundaries for Build, Deploy, and Approve
Explore how least-privilege boundaries protect CI/CD pipelines by separating build, deploy, and approval identities. Learn where secret access belongs, how immutable artifacts and approval gates reduce risk, and which audit records, rollback steps, and emergency controls support a defensible release design.
We'll cover the following...
A strong CI/CD security design clearly answers three questions: who can read a secret, who can change production, and who can authorize that change. Build, deploy, and approval use separate identities because each phase carries different risks. A build identity needs source and artifact access. A deploy identity needs authority to change a runtime environment. A release approver needs authority to promote a reviewed release, with no need to alter the artifact or administer the production environment.
The build phase produces an immutable artifact and records its origin. The build identity can access the source and artifact registry, but it cannot call the ...