Notifications
Clear all
Topic starter
17/08/2026 4:40 pm
TL;DR: Non-human identity governance is breaking down as service accounts, tokens, and AI agents outgrow human-centric IAM controls, according to WitnessAI, which argues that documented ownership, scoped access, and runtime enforcement must now sit inside one lifecycle model. Autonomous agents magnify the problem because they inherit privilege, act at machine speed, and can spawn more identities than periodic reviews can track.
NHIMG editorial — based on content published by WitnessAI: non-human identity governance, AI agents, and the five lifecycle controls
By the numbers:
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
- 80% of identity breaches involved compromised non-human identities such as service accounts and API keys.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security.
Questions worth separating out
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: Why do non-human identities increase zero trust risk?
A: Non-human identities increase zero trust risk because zero trust assumes every access request can be verified in context, but machine credentials are often distributed across code, pipelines, and third-party integrations.
Q: How should security teams govern AI agents that can choose tools at runtime?
A: Security teams should govern runtime agent choice as an access event, not as a simple application action.
Practitioner guidance
- Inventory every active non-human identity Scan application installs, OAuth grants, API keys, agent frameworks, and workload roles together so you can see what is authenticating in production.
- Assign a named human owner to each identity Bind every service account, token, workload role, and agent to a person who can approve scope changes, explain purpose, and authorise revocation.
- Right-size privileges to actual runtime need Review whether the identity can reach systems it never legitimately needs, especially when one role is reused across multiple workloads or when an agent can invoke external tools.
What's in the full article
WitnessAI's full article covers the operational detail this post intentionally leaves for the source:
- The article expands on how service accounts, OAuth tokens, workload identities, and AI agents differ in practice.
- It lays out the five lifecycle controls in more operational depth, including how to apply them across AI agents.
- It explains how named ownership and audit trails support compliance when agents act without a person present.
- It adds WitnessAI's framing of runtime enforcement across prompts, tool calls, and outputs.
👉 Read WitnessAI's analysis of non-human identity and AI agent governance →
AI agents and NHI sprawl: what is changing for IAM teams?
Explore further
17/08/2026 4:45 pm
Non-human identity governance fails when ownership is implicit rather than explicit. Service accounts, tokens, and workload identities do not carry human lifecycle signals by default, so orphaned access is the predictable outcome when ownership is left in spreadsheets or tribal knowledge. That creates a control gap across IAM, PAM, and IGA because nobody can answer who is responsible for revocation, scope changes, or exception handling. The practitioner conclusion is that every live NHI needs an accountable human owner, not just a technical system of record.
A few things that frame the scale:
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to the Ultimate Guide to NHIs.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to our Ultimate Guide to NHIs.
A question worth separating out:
Q: Who should be accountable when an AI agent causes a security incident?
A: Accountability should sit with the human owner, platform team, or business function that granted and operated the agent. The identity may act independently, but governance cannot detach responsibility from the delegation chain. Programs should define ownership, escalation, and remediation paths before deployment so responsibility is clear when the agent's behaviour changes.
👉 Read our full editorial: Non-human identity governance is breaking under agentic AI sprawl
