Because they are reusable across systems, often over-scoped, and frequently minted in automation contexts that are assumed safe. When a runner, token, or service account is compromised, the attacker can move from one system to many without additional user interaction. The risk rises sharply when rotation, revocation, and workload identity ownership are fragmented.
Why This Matters for Security Teams
Developer pipelines concentrate trust in the very places attackers target first: build runners, package registries, CI tokens, and deployment service accounts. When those non-human credentials are over-scoped, long-lived, or shared across jobs, a single compromise can turn a routine automation failure into a multi-system supply chain event. The issue is not just secrecy; it is that these identities often operate with production reach but without the governance applied to human access.
That is why this risk shows up so often in incidents tied to leaked tokens and compromised automation. NHI Management Group has documented repeated pipeline abuse patterns in CI/CD pipeline exploitation case study and in the Guide to the Secret Sprawl Challenge, where fragmented secret ownership and weak revocation practices amplify blast radius. Current guidance from OWASP Non-Human Identity Top 10 and NIST Cybersecurity Framework 2.0 both point to the same reality: machine identities must be governed as attack paths, not convenience artifacts.
In the real world, many teams discover the problem only after a build token has already been replayed across multiple repositories or cloud accounts.
How It Works in Practice
Supply chain risk rises because developer pipelines reuse non-human credentials at several layers: source control integrations, CI runners, artifact signing, package publication, and infrastructure provisioning. If one credential is embedded in a workflow or cached on a runner, an attacker who lands in that workflow can often pivot laterally without needing a human to approve each step. This is where static IAM assumptions fail. Human-oriented role design assumes stable job functions, but automation is goal-driven and path-dependent, so access needs to be evaluated at execution time.
Practically, stronger programs shift from persistent secrets to workload identity and just-in-time authorization. The identity should prove what the workload is, not merely hand it a reusable token. That usually means short-lived credentials, tightly scoped per task, and automatic revocation when the job ends. In many environments, SPIFFE-style workload identity, OIDC-issued ephemeral tokens, and policy-as-code engines help enforce this model. NIST’s identity guidance in NIST SP 800-63 Digital Identity Guidelines is still oriented toward human identity, but the operational lesson transfers: assurance must match the transaction, and assurance should be time-bound.
NHI Management Group’s The 52 NHI breaches Report shows that fragmented ownership and delayed revocation repeatedly turn a single exposed secret into a broader incident. In the secrets-management research The State of Secrets in AppSec, the average time to remediate a leaked secret is 27 days, which is far longer than the time an attacker needs to test and reuse it in automated pipelines. These controls tend to break down when pipelines span multiple clouds and third-party actions because identity, logging, and revocation are no longer managed in one place.
- Issue separate credentials per pipeline stage instead of reusing one token end to end.
- Use short TTLs and automatic revocation for runners, deploy agents, and signing jobs.
- Bind each credential to a workload identity and enforce request-time policy checks.
- Rotate secrets on compromise triggers, not just on calendar schedules.
Common Variations and Edge Cases
Tighter credential controls often increase pipeline friction, requiring organisations to balance delivery speed against reduced blast radius. That tradeoff is real, especially when legacy build systems expect long-lived keys or when vendors do not support workload identity cleanly. Best practice is evolving, and there is no universal standard for every CI/CD stack yet.
One common edge case is ephemeral infrastructure that still depends on durable bootstrap secrets. Another is GitHub Actions or similar automation that uses marketplace components, where the pipeline itself can inherit risk from a compromised dependency. The supply chain lesson is that “trusted automation” is only trustworthy if every hop has bounded privilege and independent revocation. The Reviewdog GitHub Action supply chain attack and the Shai Hulud npm malware campaign both show how attackers exploit trust chains that were assumed to be low risk.
Where teams still rely on broad deploy keys, shared service accounts, or secrets stored in repo variables, the answer is not simply “rotate faster.” The better pattern is to remove standing privilege, separate build-time from release-time authority, and make secret ownership explicit across engineering and security. That approach aligns with NIST SP 800-53 Rev 5 Security and Privacy Controls and the control themes in OWASP’s NHI guidance, but implementation details still vary by platform.
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-01 | Addresses over-scoped and reused non-human credentials in pipelines. |
| OWASP Agentic AI Top 10 | A1 | Autonomous pipeline steps can chain actions beyond intended privilege. |
| CSA MAESTRO | T1 | Covers governance for machine-to-machine trust in automated workflows. |
| NIST AI RMF | Supports risk management for dynamic, automated decision-making systems. | |
| NIST CSF 2.0 | PR.AC-4 | Least-privilege access management is central to reducing pipeline blast radius. |
Inventory every pipeline identity and replace standing access with least-privilege, per-workload credentials.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
