Id-based assaults are on the rise. Attacks during which malicious actors assume the identification of an entity to simply achieve entry to assets and delicate information have been rising in quantity and frequency over the previous few years. Some latest reviews estimate that 83% of assaults contain compromised secrets and techniques. In response to reviews such because the Verizon DBIR, attackers are extra generally utilizing stolen credentials to achieve their preliminary foothold, relatively than exploiting a vulnerability or misconfiguration.
Attackers will not be simply after human identities that they’ll assume, although. Extra generally, they’re after Non-Human Identities (NHIs), which outnumber human identities within the enterprise by at the very least 50 to at least one. In contrast to people, machines don’t have any good option to obtain multi-factor authentication, and we, for essentially the most half, have been counting on credentials alone, within the type of API keys, bearer tokens, and JWTs.
Historically, identification and entry administration (IAM) has been constructed on the concept of persistent human traits over time. It’s uncommon for an individual to vary their title, fingerprints, or DNA. We are able to assume that for those who went by an identification verification course of, you’re confirmed to be the human you declare to be. Primarily based on this, you may receive sure permissions dependent in your function throughout the group and your degree of belief.
Securing machine identities means getting a deal with on the distinctive trait that dangerous actors really care about, specifically, their entry keys. If we deal with these extremely valued secrets and techniques as the way in which to uniquely determine the identities we’re defending, then we are able to leverage that into true observability round how entry is granted and used all through your enterprise.
Accounting For NHIs By means of A Fractured Lens
Earlier than we take a deeper have a look at secrets and techniques as distinctive identifiers, let’s first contemplate how we at present speak about NHIs within the enterprise.
Most groups battle with defining NHIs. The canonical definition is solely “something that isn’t a human,” which is essentially a large set of considerations. NHIs manifest in another way throughout cloud suppliers, container orchestrators, legacy methods, and edge deployments. A Kubernetes service account tied to a pod has distinct traits in comparison with an Azure managed identification or a Home windows service account. Each staff has traditionally managed these as separate considerations. This patchwork strategy makes it practically unimaginable to create a constant coverage, not to mention automate governance throughout environments.
The exponential progress of NHIs has left a niche in conventional asset stock instruments, and entry reviewers cannot preserve tempo. Enforcement of constant permissions or security controls throughout such a wildly various set of identities appears close to unimaginable. That is on prime of ageing legacy methods that haven’t had their passwords rotated or audited in years.
Compounding this challenge is the shortage of metadata and possession round NHIs. Questions like “What is that this identification for?” or “Who owns this token?” continuously go unanswered, as the one who created and launched that identification into the system has moved on. This vacuum of accountability makes it tough to use fundamental lifecycle practices similar to rotation or decommissioning. NHIs that had been created for testing functions usually persist lengthy after the methods they had been tied to are discontinued, accumulating threat silently.
The UUIDs Of Your Zero Belief Defend Floor
It doesn’t matter what type or form an NHI takes, so as to do work as a part of an utility or system, it must authenticate to entry information and assets and do its work.
Mostly, this takes the type of secrets and techniques, which appear to be API keys, certificates, or tokens. These are all inherently distinctive and might act as cryptographic fingerprints throughout distributed methods. When used on this manner, secrets and techniques used for authentication change into traceable artifacts tied on to the methods that generated them. This permits for a degree of attribution and auditing that is tough to realize with conventional service accounts. For instance, a short-lived token will be instantly linked to a particular CI job, Git commit, or workload, permitting groups to reply not simply what’s performing, however why, the place, and on whose behalf.
This access-as-the-identifier mannequin can carry readability to your stock, providing a unified view of all of your machines, workloads, process runners, and even agent-based AI methods. Secrets and techniques supply a constant and machine-verifiable technique of indexing NHIs, letting groups centralize visibility into what exists, who owns it, and what it may entry, no matter whether or not it is operating on Kubernetes, GitHub Actions, or a public cloud.
Critically, this mannequin additionally helps lifecycle administration and Zero Belief ideas extra naturally than legacy identification frameworks. A secret is barely legitimate when it may be used, which is a provable state, which suggests unused or expired secrets and techniques will be routinely flagged for cleanup. This will cease identification sprawl and ghost accounts, that are endemic in NHI-heavy environments.
The Safety Ramifications Of Secrets and techniques At NHI Identifiers
If we’re going to speak about secrets and techniques because the distinctive identifier for machines and workloads, we do want to deal with the truth that they’ve a nasty tendency to leak. In response to our State of Secrets and techniques Sprawl 2025 analysis, virtually 23.8 million secrets and techniques had been leaked on public GitHub repositories in 2024, a 25% year-over-year enhance. Worse but, a full 35% of the personal repositories we researched contained secrets and techniques, 8 occasions as many as we present in public repositories.
Breaches over the previous a number of years, from Uber to the U.S. Division of the Treasury, have proven that when secrets and techniques are scattered throughout pipelines, codebases, containers, and cloud configs with out constant administration, they change into a silent invitation to attackers. These leaked or stolen credentials supply attackers a low-friction path to compromise.
A leaked API key or NHI token permits anybody who makes an attempt to make use of it to determine a sound session, with no mechanism in place to confirm its legitimacy or the context of its use. If the key is tied to a long-lived, over-permissioned bot or service account, the attacker immediately inherits all that belief.
The issue is amplified additional when secrets and techniques outlive their function. Orphaned secrets and techniques, credentials forgotten about and by no means decommissioned, deserted CI/CD jobs, or one-off initiatives, linger quietly, usually with harmful ranges of entry and nil visibility. With out possession, expiration, or revocation processes, they change into very best entry factors for attackers on the lookout for stealth and persistence.
GitGuardian Can Stock All Your Secrets and techniques, Not Simply The Leaked Ones
Secrets and techniques can solely dwell in two attainable locations: the place they belong, safely saved in a secrets and techniques administration vault, or leaked elsewhere. We’ve been serving to individuals discover the secrets and techniques leaked the place they don’t seem to be purported to be for years now, with our internally centered Secrets and techniques Detection providing and our Public Monitoring platform.
Now, GitGuardian can act as your cross-environment NHI stock platform, serving to you achieve visibility into what secrets and techniques are in your vaults, together with metadata round how they’re used. GitGuardian builds a unified, contextualized stock of each secret, no matter origin or format. Whether or not it is injected by way of Kubernetes, embedded in an Ansible playbook, or retrieved from a vault like HashiCorp, every secret is fingerprinted and monitored.
This cross-environment consciousness permits groups to shortly see
- Which NHIs have keys leaked publicly.
- If any inner leaks occurred for those self same secrets and techniques.
- Any secrets and techniques redundantly saved in a number of vaults
- If the key is lengthy lived and wishes rotation
 |
| The GitGuardian NHI Governance Stock dashboard exhibiting coverage violations and threat scores. |
Crucially, GitGuardian additionally detects “zombie” credentials, secrets and techniques that persist with out authorization or oversight. Wealthy metadata, like creator attribution, secret lifespan, permissions scope, and context, empower governance over these non-human actors, enabling real-time stock alignment and accountability.
This visibility is not simply operational, it is strategic. GitGuardian allows centralized coverage enforcement throughout all secret sources, remodeling reactive secrets and techniques detection into proactive identification governance. By mapping secrets and techniques to NHIs and imposing lifecycle insurance policies like expiration, rotation, and revocation, GitGuardian closes the loop between discovery, vaulting, and enforcement
Past Stock And In direction of NHI Governance
The rise of non-human identities has reshaped the identification panorama, and with it, the assault floor. Credentials aren’t simply entry keys. Secrets and techniques are the mechanism that enables an attacker to imagine an identification that already has persistent entry to your information and assets. With out visibility into the place these credentials dwell, how they’re used, and whether or not they’re nonetheless legitimate, organizations are left susceptible to silent compromise.
 |
| GitGuardian’s Secrets and techniques Safety + NHI Governance = Non-Human Id Safety |
Treating secrets and techniques because the UUIDs of recent workloads is the clearest path to scalable, cross-platform NHI governance. However that strategy solely works for those who can see the total image: vaults, pipelines, ephemeral infrastructure, and every part in between.
GitGuardian delivers that visibility. We’re turning fragmented credential sprawl right into a unified, actionable stock. By anchoring NHI identification to its authenticating secret, and layering in wealthy metadata and lifecycle controls, GitGuardian allows security groups to detect points early, determine over-permissioned and orphaned credentials, and implement revocation earlier than a breach happens.
We’re serving to complicated fashionable enterprises cut back the chance of profitable identity-based assaults. When credentials are monitored, scoped, and managed in actual time, they’re not low-hanging fruit for attackers.
We’d love to provide you a full demo of the capabilities of the GitGuardian NHI Safety platform and enable you to get unparalleled perception into your NHIs and secrets and techniques security. And for those who’d relatively discover by yourself, take a guided tour of GitGuardian with our interactive demo!
