Topic starter
02/06/2026 6:52 pm
TL;DR: Two-thirds of enterprises already have AI agents in production, and many teams still handle them like service accounts with a credential and a handoff, according to Orchid Security and Team8’s 2025 CISO Village Survey. That leaves a widening gap between intended access and what agents actually do, which makes execution visibility the real control point.
Editorial analysis by NHI Mgmt Group, based on content published by Orchid Security: “Your Agents Are Already Running. Do You Know What They're Doing?”.
Key questions
Q: What is the main governance failure in agentic identity programmes?
A: The main failure is assuming provisioned access describes actual behaviour.
Q: Why do AI agents make stale permissions more dangerous?
A: AI agents can discover and reuse stale permissions at machine speed, turning forgotten access into active exposure.
Q: How can security teams tell whether agent access is actually under control?
A: Look for evidence that the team can trace every tool call, secret use, and cross-system action back to a named owner and a valid approval path.
Practitioner guidance
- Map agent-to-origin identity chains Record which human, application, or workload identity each agent acts on behalf of, including inherited permissions and delegated authority.
- Inventory identity dark matter before deployment Find stale permissions, migration residue, and old access grants that an agent could reuse without any new approval.
- Add runtime agent observability Log access paths, authorization decisions, and cross-system actions so you can reconstruct what actually happened in each session.
Bottom line: Agentic identity turns access governance into a runtime verification problem because the critical question is no longer only who was granted access.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/06/2026 7:05 pm
Agentic identity is a runtime governance problem, not a provisioning problem. The article shows that the real issue is the gap between what an identity was intended to do and what an agent actually executed across systems. That makes runtime visibility the decisive control plane for agentic behaviour. For practitioners, the key shift is to govern action sequences, not just entitlements.
A question worth separating out:
Q: What should IAM teams do when agents act on behalf of existing identities?
A: They should govern the delegation chain as a first-class identity object. That means linking the agent to its originating identity, reviewing inherited authority, and checking whether the runtime path still fits the intended business use. Without that linkage, accountability breaks down quickly.
👉 Read our full editorial: Agentic identity exposes the gap between intended and actual access