article --summary
The summary
This vendor article uses a recent supply chain attack on GitHub repositories to make a point about leaked credentials: removing a secret from the latest code does not make it safe, since it may persist in commit history, remain active, or be copied into tickets, logs, and other tools. The reader learns why discovery matters, and why revoking or rotating a live credential comes before anything else.
The second half covers what comes after discovery. Putting a replacement key back into source code just recreates the problem, so the article recommends storing credentials in a central manager, having applications fetch them at runtime, and using short-lived dynamic credentials where a service supports them. It also notes that many static credentials will remain, and those still need controlled access and rotation.
The article's main takeaway is that the goal is to reduce the number of unmanaged credentials that can be stolen, not just to clean up a repository. It promotes two HashiCorp products, Vault Radar for finding exposed secrets and Vault for managing them, and points to a credential risk whitepaper for more detail.
Editorial note: This is a summary of an article first published by HashiCorp Blog. The full piece is on their site.