Topic starter
11/11/2026 6:01 pm
TL;DR: Borrowed user identity leaves AI agent activity hard to distinguish from human activity, according to IndyKite. Enterprise governance then loses the ability to attribute requests, scope delegated authority, and prove why access was permitted.
Editorial analysis by NHI Mgmt Group, based on content published by IndyKite: “Meta's Muse and the enterprise risk of AI agent access you can’t see”.
Key questions
Q: Why do shared user accounts make AI agent activity hard to govern?
A: Shared user accounts hide which AI agent acted, so approvals, logging and revocation cannot be tied to a specific autonomous system or accountable human.
Q: How does delegated authority for AI agents work in practice?
A: Delegated authority works by letting an AI agent act under a human-granted scope that is limited to specific tools, data, actions, and time windows.
Q: What should teams do first when an AI agent borrows user access?
A: Assign the agent its own identity, then bind it to a named human owner, a limited role, and explicit per-tool permissions before it can act.
Practitioner guidance
- Issue agents separate principals Create distinct identities for approved agents instead of letting them operate under a human user's account or token.
- Enforce per-request authorization Evaluate each agent action against delegated purpose, requester relationship and data sensitivity rather than relying on a one-time consent event.
- Centralize audit evidence for agent actions Record who tasked the agent, what authority it used, what policy applied and what it changed in enterprise monitoring systems.
Bottom line: AI agents that reuse a human account create an attribution problem that standard access reviews are not designed to solve.
Glossary terms: Agentic AI, Delegated authority, Per-Request Authorization, Distinct Agent Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:08 pm
Borrowed identity is an accountability failure, not just a visibility gap. When an AI agent acts under a human account, the enterprise no longer has a clean boundary between human intent and machine execution. That creates an attribution problem in audit, incident response and access governance. The practitioner conclusion is simple: treat the agent as a separate actor or lose the ability to govern its behaviour.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What evidence should security teams capture for AI agent actions?
A: Capture the policy decision, the identity used, the human owner, the tool or data touched, the request parameters, the outcome, and the timestamp. Those records let teams reconstruct what the agent was allowed to do, what it actually did, and whether a control denied or approved the action.
👉 Read our full editorial: Borrowed identities let AI agents act with hidden permissions