Glossary / practitioner hardening supply-chain cloud

CI/CD secrets (GitHub Actions)

Your build pipeline holds the keys to your cloud and your package registries. Anyone who can push to the repository can usually read them, so scope them small and prefer short-lived tokens.

A CI/CD pipeline builds, tests and ships code automatically. To do that it needs credentials: cloud keys, registry tokens, signing keys. In GitHub Actions these are stored as repository, environment or organisation secrets and handed to workflows when they run.

GitHub's own security guidance says the key fact plainly: any user with write access to a repository has read access to all secrets configured in it. So a stolen developer account with write access is, in practice, a stolen copy of every secret that repository's workflows can see. The November 2026 wfx-loot campaign (see the news card) worked this way: compromised accounts pushed a workflow change that sent secrets out, then deleted the run.

What GitHub's guidance tells you to do

Give workflow credentials the least privilege they need. Set the default GITHUB_TOKEN permission to read-only for repository contents and raise it only for the jobs that need more.

Where your cloud provider supports OpenID Connect (OIDC), let workflows authenticate directly to it instead of storing long-lived cloud keys as secrets.

Do not store structured data (a JSON, XML or YAML blob) as one secret, because log redaction relies on an exact match and may fail; create one secret per value. Register any sensitive value a workflow generates, such as a signed JWT, as a secret so it is redacted too. If an unredacted secret reaches a run log, delete the log and rotate the secret.

Treat pull_request_target and workflow_run triggers with care: combined with a checkout of an untrusted pull request they run privileged, with possible write access and access to secrets.

Pin third-party actions to a full-length commit SHA (or a workflow dependency lockfile where you can use one), keep them current with Dependabot, and use CODEOWNERS so changes under .github/workflows need a designated reviewer.

Self-hosted runners are not guaranteed to be clean and ephemeral and can be persistently compromised by untrusted workflow code; GitHub says they should almost never be used for public repositories.

CyberStack guidance (our own advice, not GitHub's)

Keep an inventory of which repositories hold which secrets, and who has write access to each. Write access is a secrets-reader role; review it like one, and require phishing-resistant MFA for everyone who has it.

Watch for workflow runs that are missing from the run history, new short-lived branches, and edits to .github/workflows from accounts that do not normally touch them.

If a pipeline secret may have leaked, rotate first and investigate second, and check whether the same credential could publish packages your customers install.

See also:

Fact source: GitHub Docs — Secure use reference (GitHub Actions).