Join our Newsletter — 33% off our NHI Course

Do OIDC-run CI/CD pipelines still leave secrets exposed?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Akeyless's analysis of CI/CD pipelines finds they often hold the most privilege in the estate, while public GitHub exposed nearly 29 million new secrets in 2025. Runtime issuance, narrow scope, and fast revocation are the controls that shrink the blast radius when pipeline authority outlives the task.

Editorial analysis by NHI Mgmt Group, based on content published by Akeyless: “The Hidden Risks of Secrets Mismanagement in CI/CD Pipelines”.

By the numbers:

Key questions

Q: Why do CI/CD secrets create more risk than many teams expect?

A: CI/CD secrets often have broad blast radius because they can authenticate to source control, cloud platforms, package registries, and deployment systems.

Q: What are the signs that pipeline secrets are not under control?

A: Common warning signs include credentials in source code, config files, or CI/CD variables, broad permissions that exceed the job's needs, and tokens that remain valid after a pipeline has been retired or replaced.

Q: What breaks when secrets are hardcoded into DevOps pipelines?

A: Hardcoded secrets break rotation, ownership, and offboarding at the same time.

Practitioner guidance

  • Implement runtime-only credential delivery Replace stored pipeline secrets with short-lived values issued at job execution time and scoped to the specific step that needs them.
  • Separate build and production identities Use distinct service accounts and permissions for build, test, staging, and production promotion so one compromised runner cannot inherit the full deployment path.
  • Scan the commit and artifact chain Run pre-commit hooks, CI scanners, and scheduled history scans across source, logs, and container layers so exposed secrets are caught before they spread.

Bottom line: CI/CD secrets become a governance failure when pipeline authority outlives the job that needed it.

Glossary terms: CI/CD secret, Ephemeral Runner, Dynamic Secret, Pipeline Credential

What's in the full article

Akeyless's full guide covers the operational detail this post intentionally leaves for the source:

  • Workflow examples for injecting secrets at runtime without storing them in YAML or source code
  • Step-by-step detection patterns using pre-commit hooks, CI scanners, and repository history scans
  • Operational guidance for OIDC federation in GitHub Actions and other cloud-integrated pipelines
  • Rotation and revocation patterns for credentials that may already exist in logs, history, or artifacts

👉 Read Akeyless's guide to CI/CD secrets management gaps and production exposure →

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

CI/CD secrets exposure is a privileged identity problem, not just a scanning problem: Pipeline credentials often have the authority to deploy, configure, and query production systems. That makes them non-human identities with unusually high blast radius when leaked. The governance mistake is assuming that build infrastructure is temporary enough to be low-risk. In reality, the access it carries is durable and consequential, so practitioners should govern pipeline identities as production actors.

A few things that frame the scale:

  • 28.65 million new hardcoded secrets were detected in public GitHub commits in 2025 alone, a 34% year-over-year increase and the largest single-year jump ever recorded, according to the State of Secrets Sprawl 2026.
  • 28% of secrets incidents now originate outside code repositories, in Slack, Jira, and Confluence, and are 13% more likely to be categorised as critical than code-based leaks, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: Should teams use OIDC federation or stored cloud keys for CI/CD access?

A: Use OIDC federation when the pipeline only needs cloud access for a specific run, because it removes the long-lived key problem entirely. Stored keys should be reserved for edge cases that cannot support federated issuance, and even then they need strict scoping and aggressive rotation.

👉 Read our full editorial: CI/CD secrets management gaps keep production access exposed



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.