Problem Statement
Outline concrete steps to harden a C I platform against supply chain attacks.
Explanation
Run builds on ephemeral workers. Isolate secrets and prefer O I D C federation to cloud over long-lived keys. Restrict who can modify pipelines and who can approve releases. Pin actions and plugins by digest. Scan build images and runners. Sign artifacts and generate provenance in CI, then verify in the deploy gate. Log everything to a central trail. These steps remove silent back doors and make tampering noisy.
Code Solution
SolutionRead Only
Pin: uses: org/action@sha256:…; runners ephemeral; least-priv tokens; admission enforces signature + provenance
