TL;DR: The gap is GitGuardian's 45:1 non-human-to-human ratio in enterprise environments, which shows why IAM programmes built around people leave machine credentials under-governed. Machine identities need inventory, ownership, lifecycle control, and privilege revalidation before their access turns into audit and security debt.
Editorial analysis by NHI Mgmt Group, based on content published by GitGuardian: “IAM Strategy for CISOs: Securing Non-Human Identities”.
Key questions
Q: What problem does ownership attribution solve for service accounts and API keys?
A: It closes the gap between exposure detection and accountable remediation.
Q: How can organisations tell whether NHI governance is actually working?
A: NHI governance is working when every machine identity has an owner, a purpose, a minimum-necessary entitlement, and evidence of rotation and review.
Q: What breaks when non-human identities are managed outside the IAM operating model?
A: What breaks is accountability.
Practitioner guidance
- Inventory every non-human identity Map service accounts, API keys, tokens, and certificates across code, chat, ticketing, and vault systems so you can identify where machine access actually exists.
- Establish a single authoritative secret source Consolidate duplicate credentials into the approved enterprise secrets manager and remove unmanaged copies from other stores and repositories.
- Tie rotation to privilege revalidation Review permissions whenever a machine credential is rotated so the replacement secret does not inherit excess access from the old one.
Bottom line: Non-human identities create a governance blind spot when IAM programmes are still built around people rather than credentials that power workloads and automation.
Glossary terms: Non-Human Identity (NHI), Secrets Sprawl, Standing Access, Lifecycle Governance
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Non-human identity governance is now a core IAM control plane, not a side concern. IAM programmes that stop at employees and contractors are already incomplete because a large share of enterprise access is exercised by machines. Those identities carry real privilege, real blast radius, and real audit obligations. The practitioner conclusion is straightforward: if the governance model does not cover service accounts, API keys, tokens, and certificates, it is not an enterprise IAM model.
A few things that frame the scale:
- 68% of organisations do not know how to fully address NHI risks, according to the Ultimate Guide to NHIs.
- Enterprises manage far more machine secrets than human ones: 20 times as many according to Enterprise Strategy Group, and 45 times according to GitGuardian.
A question worth separating out:
Q: Should organisations manage human and machine identities under the same access governance model?
A: They should govern them under the same programme, but not with identical controls. The shared requirement is visibility into who or what is authorised. The difference is that machine identities usually need tighter ownership, shorter lifecycle expectations, and clearer operational handoff. A single programme works best when it distinguishes subject type while keeping one governance record.
👉 Read our full editorial: Non-human identities need their own governance inside IAM