Topic starter
16/04/2026 8:01 pm
TL;DR: Agentic AI is moving into enterprise workflows faster than identity governance can track, with Delinea citing 87% of organisations saying their posture is ready for AI at scale while 46% admit governance is deficient. The deeper problem is that autonomous systems compress decision, access, and action into a window current identity controls were not built to govern.
Editorial analysis by NHI Mgmt Group, based on content published by Delinea: “Nothing happening is everything—especially in the age of agentic AI”.
By the numbers:
- 87% of organizations say their identity security posture is prepared to support AI at scale.
- 46% of respondents acknowledge that their identity governance around AI systems is deficient.
- 82 to 1 is the ratio by which non-human identities already outnumber human identities.
Key questions
Q: What breaks when AI SOC autonomy is not tightly governed?
A: The platform can take actions that outgrow the permissions, escalation rules, and accountability model the organisation intended.
Q: Why do agent-to-agent workflows create more identity risk than single-agent automations?
A: Because each agent handoff introduces another authorisation decision, another trust boundary, and another place where accountability can blur.
Q: How do security teams know if AI governance is working?
A: Look for evidence that access decisions are reviewable, permissions are revocable, and exceptions are not becoming permanent.
Practitioner guidance
- Instrument runtime agent visibility Track which agent initiated each action, which identity it used, and which downstream systems accepted that request so privileged behaviour is attributable in real time.
- Define delegation boundaries for agent swarms Set explicit rules for which agent may trigger, approve, or inherit access from another agent, and block implicit privilege propagation between autonomous components.
- Reduce standing access for non-human identities Replace persistent permissions with contextual, task-scoped access so an agent does not retain broad privileges after the work it was authorised to do is complete.
Bottom line: Agentic AI turns identity into a runtime governance problem because agents request access, execute actions, and adapt in the same operating window.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/10/2026 2:36 am
Agentic AI exposes an identity control problem, not just an AI adoption problem: the article shows that systems are already acting, delegating, and adapting inside enterprise workflows. That means identity is no longer a perimeter service around AI use, it is the runtime control plane for AI behaviour. Practitioners should stop treating agentic AI as a future-state issue and govern it as an active identity domain now.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations loosen access controls to support AI automation?
A: Only with caution. The article shows that speed pressure often drives broader permissions and longer access durations, but that approach increases exposure when agents operate continuously. The safer decision is to constrain the privilege window, preserve attribution, and prove that the access model still matches the agent’s actual task.
👉 Read our full editorial: Agentic AI is outpacing identity control and visibility