TL;DR: Oak's July 30 analysis finds AI agent governance breaks down when discovery, ownership, and effective access are treated as separate tasks. Static registries can look complete while shadow agents, stale owners, and overbroad reach remain unresolved.
Editorial analysis by NHI Mgmt Group, based on content published by Oak: “Build or Buy Identity Governance for AI Agents”.
By the numbers:
- The 2026 Identity Security Landscape survey counted 109 machine identities per human.
- 40% of machine identities already have access to organizational data.
Key questions
Q: Why do AI agents create more risk when access is scoped once but not rechecked during execution?
A: AI agents can move through many steps in a single task, including prompts, retrieval, tool use, and output.
Q: How should organisations decide whether to build or buy AI governance controls?
A: Choose build when the organisation needs deep custom instrumentation, strict data residency, and has dedicated engineering capacity to own the system long term.
Q: What breaks when AI agent identity governance relies on a manual registry?
A: Manual registries miss shadow agents, stale ownership, and changes made outside the recording path.
Practitioner guidance
- Audit discovery coverage against source systems Map every agent source you rely on, including cloud consoles, SaaS platforms, homegrown workflows, and MCP-connected tools, then compare that list to what your current registry actually sees.
- Calculate effective permissions, not just declared scopes Trace nested groups, inherited admin rights, and impersonation chains to determine what each agent can truly reach before you approve or renew access.
- Tie each agent to a current accountable owner Replace static owner fields with a live mapping that updates when people change teams or leave, so review and remediation always have a responsible human.
Bottom line: Homegrown AI agent governance fails when discovery, ownership, and effective access are managed as separate tasks instead of one lifecycle problem.
Glossary terms: AI Agent Identity Governance, Effective Permissions, Shadow Agent, Accountable Owner
What's in the full article
Oak's full blog post covers the operational detail this post intentionally leaves for the source:
- How ConnectAny reaches SaaS, homegrown, shadow, and custom agents through direct API, database, file, and on-prem connectors
- The line-by-line build-versus-buy comparison showing where homegrown scripts stop short on discovery, ownership, and remediation
- The evidence Oak says auditors and boards want to see, including inventory completeness and worst-case reachable access
- The review and remediation flow used to remove excessive permissions at the source rather than through ticket handoff
👉 Read Oak's analysis of build versus buy for AI agent identity governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Shadow agent discovery is the first governance failure, not a secondary control gap: A homegrown inventory can only govern the agents someone remembered to register. That means the programme loses coverage exactly where risk is highest, in ad hoc agents created outside formal approval paths. The implication is simple: identity governance for agents starts with discovery from source systems, not with registration hygiene.
A few things that frame the scale:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to the Ultimate Guide to NHIs.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should identity teams do when an AI agent leaves the original owner's control?
A: Treat that as an ownership and lifecycle event, not a minor metadata update. The agent needs a current accountable human, a fresh review of its effective permissions, and source-level removal of any excess access that no longer matches its purpose.
👉 Read our full editorial: Identity governance for AI agents fails when discovery and ownership break