Join our Newsletter — 33% off our NHI Course

Why does push-to-vault still leave secrets exposed too long?

 

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

TL;DR: 28.65 million new hardcoded secrets in public GitHub commits in 2025 points to a wider leak-and-remediate problem, GitGuardian says from its telemetry. Vaulting only helps when detection, rotation, and revocation close quickly enough to cut off reuse.

Editorial analysis by NHI Mgmt Group, based on content published by GitGuardian: “From Detection to Defense: How Push-to-Vault Supercharges Secrets Management for DevSecOps”.

Key questions

Q: Why do leaked secrets create operational risk even after they are discovered?

A: A leaked secret remains dangerous because it can still be active and usable until it is revoked.

Q: How do security teams know whether push-to-vault remediation is actually working?

A: Look for a shrinking gap between detection and controlled storage, plus clear evidence that vaulted incidents are followed by successful rotation and revocation.

Q: What breaks when secrets are still stored outside managed vaults?

A: Secrets become easy to reuse across humans, scripts, and agents without a consistent audit trail.

Practitioner guidance

  • Define a vault-first remediation workflow Make every detected secret follow a standard path from exposure to approved vault location, runtime update, rotation, and closure evidence.
  • Restrict write access to controlled vault paths Limit automation to named namespaces, approved environments, or dedicated paths so a remediation tool cannot scatter credentials across the vault estate.
  • Map each secret to its non-human identity Record which service account, pipeline, or workload depends on the credential before closing the incident so rotation and revocation are coordinated.

Bottom line: The main risk is not just that secrets leak, but that leaked credentials remain valid long enough to keep granting access.

Glossary terms: Push-to-vault, Secrets Sprawl, Non-Human Identity Lifecycle, Vault remediation

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: 20712
 

Push-to-vault closes a governance gap, not just a tooling gap: detection is only useful when it is paired with a controlled path into a secret manager. GitGuardian is right to frame the last mile as the real failure point, because exposure without vaulting leaves the credential in governance limbo. The practitioner conclusion is simple: remediation must become a governed workflow, not a manual afterthought.

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.
  • Only 44% of organisations are currently using a dedicated secrets management system, according to the 2024 State of Secrets Management Survey.

A question worth separating out:

Q: Should organisations treat Vault observability as an IAM control?

A: Yes. Vault observability is part of identity assurance because it links authentication, entitlements, and secret use into one governance view. Without that linkage, teams cannot tell whether a secret was accessed by a sanctioned workload, a shadow admin, or an unauthorised identity path.

👉 Read our full editorial: Push-to-vault workflows close the gap in secrets governance



   
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.