Notifications
Clear all
Topic starter
14/08/2026 6:37 pm
TL;DR: Agentic identities break the old human versus machine split because they act on behalf of a prompter, need task-scoped privilege, and require continuous observability at the application layer, according to Orchid Security. Standing access, periodic review, and identity inventory models are too slow for agentic behaviour, so governance has to move to runtime attribution and dynamic enforcement.
NHIMG editorial — based on content published by Orchid Security: A practical framework for governing agentic identities before they govern themselves
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do standing privileges increase risk for AI agents?
A: Standing privileges increase risk because the agent keeps a valid path into systems even when the original need has passed.
Q: How can organisations tell whether AI agent governance is actually working?
A: Look for evidence that agent access is ephemeral, traceable, and constrained at the action level.
Practitioner guidance
- Inventory every agent as a governed identity Create a registry for each AI agent with owner, delegated human principal, scope, and approved systems.
- Replace standing agent access with JIT task grants Bind access to the task, not the deployment.
- Instrument application-layer observability for agent behaviour Capture real-time resource access, authorisation decisions, and action context in the systems where agents actually operate.
What's in the full report
Orchid Security's full article covers the operational detail this post intentionally leaves for the source:
- The full delegated-identity framework for attributing agent actions to a human principal and proving scope.
- The practical sequencing for moving from inventory to hygiene remediation, observability, and dynamic privilege.
- The source discussion of agentic dark matter and how unmanaged agents fit into a broader identity programme.
- The applied examples showing how application-layer visibility differs from ordinary log review.
👉 Read Orchid Security's framework for governing agentic identities →
Agentic identities: what does delegated access change for IAM teams?
Explore further
14/08/2026 6:44 pm
Delegated identity is the only defensible way to govern agentic action. Agentic systems are not independent principals in the IAM sense, but they are also not ordinary machine identities with fixed purpose. The security model has to preserve the link from human intent to machine execution, or attribution collapses the moment an investigation begins. Practitioners should treat the delegation chain as a first-class identity object, not an audit afterthought.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials, according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: What is the difference between agentic identity governance and traditional NHI control?
A: Traditional NHI control focuses on static credentials, lifecycle hygiene, and least privilege for systems that do not change intent mid-session. Agentic identity governance adds delegation, runtime scope checks, and application-layer observability because the actor can alter behaviour while still appearing to use legitimate access.
👉 Read our full editorial: Agentic identity governance needs delegated access and live observability
