Skip to main content
Webinar Learn how to move from vulnerability insights to governed remediation across complex infrastructure environments Join the webinar

From exposed secrets to managed credentials: Reducing credential risk across the application lifecycle

Learn how Vault Radar and Vault help organizations find exposed secrets, improve remediation, and reduce credential risk across the application lifecycle.

A recent software supply chain attack affecting tens of thousands of GitHub repositories highlights a security problem that is easy to underestimate: a credential does not stop being exposed simply because it has been deleted from the latest version of the code. 

Researchers uncovered a campaign in which attackers inserted a malicious GitHub Actions workflow into repositories they had permission to modify. Designed to look like a routine security audit, the workflow instead searched for and exfiltrated credentials. It targeted secrets available to GitHub Actions, but also searched repository files and complete Git history for credentials associated with cloud providers and AI services. That meant credentials developers had previously committed and later removed could still be discovered. 

The incident is another reminder that responding to exposed credentials requires more than cleaning up source code. Organizations need to understand where credentials have been exposed, remediate those credentials and ultimately improve how they are managed. HCP Vault Radar and HashiCorp Vault can help teams address different parts of that lifecycle, moving from discovering exposed secrets to bringing credentials under centralized management. 

»A deleted secret can still be an exposed secret 

Accidentally committing a credential is not an unusual scenario in software development. An API key gets added to a configuration file while testing an integration, a cloud credential helps get a prototype running, or a token is placed into a workflow to solve an immediate problem. A developer may eventually identify the mistake and remove the credential, leaving the current version of the application looking clean. 

But removing the plaintext value does not necessarily remediate the underlying credential. The secret can remain in Git history, the original credential may still be active, and copies may exist in other places across the development lifecycle. In this attack, that distinction was particularly important because the malicious workflow specifically searched historical repository content for credentials. 

HCP Vault Radar helps teams find exposed and unmanaged secrets across development environments, including credentials that persist in Git history. That visibility can help security teams understand where credential exposure exists and prioritize remediation, particularly when a secret may no longer appear in the latest version of the repository. 

Finding the exposure, however, does not address the credential itself. If a discovered credential remains active, teams still need to investigate the exposure and revoke or rotate the credential with the relevant provider. 

»Move from discovery to remediation 

Once the exposed credential has been addressed, teams also need to consider how the replacement credential will be managed. Generating a new credential and putting it back into source code or another configuration file may resolve the immediate exposure, but it recreates the same underlying problem. 

This is where Vault complements the discovery capabilities of Vault Radar. Vault provides a centralized way to secure credentials and control how applications access them. Instead of embedding a replacement credential in source code, teams can bring the credential under management in Vault and update the application, agent, or workload to retrieve it when needed. The application can still get the credential where it needs it without putting the credential back into source code. 

Where supported, organizations can take that model further by using dynamic, short-lived credentials instead of relying on long-lived static credentials. A long-lived credential discovered in an old commit could remain useful to an attacker until someone identifies the exposure and revokes it. Short-lived credentials reduce that window because they are created when needed and expire after a defined period. 

Not every application or third-party service supports dynamic credentials, so static credentials will continue to be part of many environments. Those credentials still benefit from centralized management, controlled access and rotation rather than being distributed throughout source code and development workflows. 

Together, Vault Radar and Vault create a more complete path from credential exposure to credential management. Radar goes beyond scanning source code by helping teams discover exposed and unmanaged secrets across the broader development ecosystem and providing the context needed to investigate and prioritize findings. Vault then provides the management layer for securing those credentials, controlling access and reducing reliance on long-lived credentials where possible. The combination helps teams move beyond finding exposed secrets toward reducing the unmanaged credentials that created the risk in the first place. 

»Credential exposure extends beyond source code 

Git repositories are also only one place credentials can escape. The same credential can move across the software development lifecycle as teams build, test and troubleshoot applications, appearing in tickets, documentation, collaboration systems, cloud storage, CI/CD logs and artifacts, or other development environments. Even after the original secret is removed from source code, copies can remain across the tools and systems developers use every day. 

That makes broader visibility important when responding to an exposed secret. Instead of treating a finding as an isolated string in a single repository, security teams need to understand where else that credential may have spread and the context surrounding the exposure.  

Vault Radar extends secret discovery across supported developer and collaboration environments, cloud infrastructure and software artifacts, helping teams identify credential exposure beyond source code. Combined with Vault, teams can use that visibility not only to remediate individual findings, but also to bring exposed credentials back under a more consistent management model. 

»From exposed secrets to managed credentials 

The lesson from this latest attack is not that better secrets management can prevent every software supply chain compromise. The attack began with malicious access to repositories and involved a broader compromise of the software development process. But it also shows how exposed credentials can increase the impact of an attack once an attacker gets inside. 

That makes credential security an important part of reducing the potential blast radius. Teams need a way to find credentials that have escaped, remediate the immediate exposure and improve how those credentials are managed going forward. 

Vault Radar helps identify exposed and unmanaged secrets so teams can understand where credential risk exists. Vault provides the management layer for securing credentials, controlling access, rotating secrets and, where supported, replacing long-lived credentials with dynamic, short-lived access. 

The goal is not simply to remove a secret from a repository. It is to reduce the number of unmanaged credentials available to steal and establish a lifecycle for keeping credentials secure after they are discovered. Deleting the secret may clean up the code. Remediating the credential and changing how it is managed addresses the risk. 

»Get started 

Finding an exposed secret is only the first step. Learn how organizations can build a more resilient approach to credential risk, from identifying exposures to improving how credentials are managed across the application lifecycle, in the credential risk whitepaper. 

Explore Vault Radar to uncover unmanaged and exposed secrets across development workflows, and HCP Vault Dedicated to bring credentials under centralized secrets management and reduce reliance on long-lived credentials where possible. 

 

 

More posts like this