Join our Newsletter — 33% off our NHI Course

What happens when 64% of secrets stay active after discovery?

 

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

TL;DR: Exposed secrets often stay active long after discovery, with 64% of secrets found in 2022 still exploitable four years later, according to Aembit. Secret remediation has to reach revocation, dependency mapping and cleanup, or detection keeps turning into recurring risk.

Editorial analysis by NHI Mgmt Group, based on content published by Aembit: “Secret Remediation Best Practices: A Step-by-Step Guide”.

Key questions

Q: Why do exposed secrets keep creating risk after they are detected?

A: Because detection does not stop a credential from remaining valid, and exposed values often persist in repositories, logs, backups, and configuration files.

Q: How can security teams tell whether third-party secret remediation is actually working?

A: Remediation is working when exposed secrets are revoked or rotated quickly, ownership is clear, and the same credential does not keep reappearing in code, logs or deployment files.

Q: What breaks when an exposed secret is rotated without updating every dependent system?

A: Rotating one credential without updating all consumers usually creates an outage rather than a clean fix.

Practitioner guidance

  • Map secret dependencies before revocation Identify every service, environment and pipeline that consumes the exposed credential so you can rotate without breaking production.
  • Automate revocation for exposed secrets Use vault APIs, cloud controls or incident automation to invalidate the credential as soon as its blast radius is understood.
  • Scrub the old secret from every trace Remove the credential from git history, config files, logs, build artefacts, runbooks and backup images before closing the incident.

Bottom line: The article shows that exposed secrets are usually found quickly, but remediation often fails because the credential remains valid after discovery.

Glossary terms: Secret Remediation, Standing Credential, Blast Radius, Identity-Based Authorization

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
 

Secret remediation is a lifecycle control problem, not a detection problem. The article makes clear that discovery is fast but retirement is slow, and that gap is where risk persists. A secret that is found but not fully revoked remains an active identity asset, which means governance has failed at the handoff between detection and lifecycle closure. Practitioners should judge programmes by how reliably they end credential usefulness, not by how quickly they raise an alert.

A few things that frame the scale:

  • 64% of valid secrets leaked in 2022 are still valid and exploitable today, proving that detection alone is not enough without automated revocation, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: Should organisations choose dynamic credentials over static secrets everywhere?

A: Not everywhere. Dynamic credentials are the better default where applications and platforms can handle short-lived issuance and renewal, but some legacy systems still require static secrets. The right decision is to prioritise dynamic access for high-risk paths first, then reduce static exceptions through migration and tighter ownership.

👉 Read our full editorial: Secret remediation exposes why static credentials keep failing



   
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.