Standing tokens remain usable long after the moment they were created, so a compromise can persist through normal operations and even through partial remediation. In supply chain environments, that means one stolen token can be reused to push artefacts, alter tags, or seed downstream packages. Short-lived access and verifiable revocation are the controls that reduce that exposure.
Why Standing CI/CD Tokens Become High-Value Supply Chain Targets
Standing CI/CD tokens are dangerous because they outlive the task that created them. A token that still works tomorrow, next week, or after an incident response window becomes reusable access to build systems, signing steps, package registries, and deployment APIs. In supply chain attacks, that turns a single credential theft into a durable path for artefact tampering, tag manipulation, and downstream compromise. The risk is not just theft, but persistence.
NHIMG research on the The State of Secrets Sprawl 2026 shows that 59% of compromised machines in a major 2025 supply chain attack were CI/CD runners rather than personal workstations, which is a strong signal that pipeline identity is now a primary attack surface. The same report also notes that 64% of valid secrets leaked in 2022 are still valid and exploitable today, underscoring why detection without revocation is not enough. Current guidance from the OWASP Non-Human Identity Top 10 treats long-lived machine credentials as a structural weakness, not a tuning issue.
In practice, many security teams discover CI/CD token abuse only after a package, image, or release artifact has already been trusted downstream.
How Short-Lived Access Changes the Attack Path
The practical alternative is to stop treating pipeline access like a standing account and start treating it like a per-job workload identity. A CI/CD runner should authenticate with a cryptographic identity, receive scoped access only for the current action, and lose that access automatically when the job ends. That is the operational logic behind workload identity systems such as SPIFFE and short-lived OIDC-based federation, where the system proves what the workload is rather than relying on a reusable secret.
For build and release workflows, the control model usually combines three parts:
- Ephemeral credentials issued just in time for a specific job or step.
- Policy checks at request time, not broad permissions granted in advance.
- Automatic revocation or natural expiry so stolen tokens do not remain useful.
This maps closely to the direction described in 52 NHI Breaches Analysis and the Guide to the Secret Sprawl Challenge, where exposed credentials repeatedly show up as the root cause of broader compromise. It also aligns with the NIST Cybersecurity Framework 2.0 emphasis on protecting assets and managing identity risk, plus the NIST SP 800-53 Rev 5 Security and Privacy Controls approach to least privilege and credential lifecycle control.
These controls tend to break down when legacy runners, shared service accounts, or manually rotated release keys are embedded in tightly coupled build pipelines because the credential is still needed after the job boundary has passed.
Where the Guidance Gets Hard in Real Environments
Tighter token controls often increase operational overhead, so organisations have to balance release velocity against security assurance. That tradeoff is especially sharp in multi-repo build farms, cross-org package publishing, and hybrid environments where some tools still expect long-lived API keys. Current guidance suggests that not every token must be eliminated immediately, but every standing token should be inventory-backed, narrowly scoped, and paired with monitored revocation paths.
There is no universal standard for this yet, but the direction is clear in both NHI and agentic security research. NHIMG’s Top 10 NHI Issues and Ultimate Guide to NHIs — Why NHI Security Matters Now both frame secrets sprawl as an identity governance problem, not only a secrets-management problem. External advisories from CISA cyber threat advisories reinforce the same operational lesson: exposed credentials are often reused faster than defenders can respond. In real supply chain incidents, the hardest edge case is not a single leaked token, but a web of cached credentials, inherited trust, and automation that keeps publishing after the first compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10, OWASP Agentic AI Top 10 and CSA MAESTRO address the attack and risk surface, while NIST AI RMF and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-03 | Addresses long-lived machine secrets that persist after compromise. |
| OWASP Agentic AI Top 10 | CI/CD automation shares the same dynamic authorization risk as agents. | |
| CSA MAESTRO | Covers runtime control of autonomous or automated workload identities. | |
| NIST AI RMF | Supports governance for dynamic, context-driven automation risk. | |
| NIST CSF 2.0 | PR.AC-4 | Least-privilege access control is central to pipeline token safety. |
Bind pipeline actions to ephemeral workload identity and continuous policy checks.
Related resources from NHI Mgmt Group
- Why do CI/CD secrets create such a large blast radius in supply chain attacks?
- Why do compromised CI/CD credentials make supply chain attacks much worse?
- Why do CI/CD tokens and maintainer credentials matter so much in supply chain security?
- Why do CI/CD tokens increase supply chain risk when they are over-scoped?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 21, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
