Join our Newsletter — 33% off our NHI Course

Could runtime authorisation govern agentic control better than identity?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: Runtime authorisation, with Willow reporting that a single prompt can trigger tool use, data access, delegation, and export decisions across systems, is the point of control. Agent workflows need policy to decide before execution, or audit and revocation come too late.

Editorial analysis by NHI Mgmt Group, based on content published by Willow: “Agentic Control Plane: Governing Enterprise AI at Runtime”.

Key questions

Q: Why do shared service accounts make agent governance harder?

A: Shared service accounts make it harder to prove which employee initiated the work and which agent actually performed it.

Q: What breaks when agent approval workflows are the only control on autonomous actions?

A: Approval-only models fail when the agent can assemble and execute a sequence too quickly for review to be meaningful.

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.

Practitioner guidance

  • Map every agent execution path Inventory the employee, agent, machine user, tool, data class, and approval path for each workflow so governance can follow the full chain.
  • Separate tool access from action rights Grant read, create, update, export, and delete rights independently so access to a system never implies full use of its functions.
  • Require inline policy checks before execution Evaluate user, agent, tool, action, data, and context before the agent calls the backend system, then block or narrow the request when policy fails.

Bottom line: The article’s central claim is that enterprise AI needs runtime governance for actions, not just authentication for people.

Glossary terms: Runtime Authorisation, Agentic Data Control Plane, Function-Level Permissions, Identity Lineage

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Runtime governance is the new control plane for enterprise AI: once an agent can choose tools, move context, and complete actions before a human reviews the output, classic identity governance stops at the wrong layer. The article correctly reframes the problem as action governance, not just authentication. That is the level where policy, context, and audit must meet if organisations want usable AI without open-ended privilege. Practitioners should treat runtime enforcement as a first-class identity function, not an integration detail.

A few things that frame the scale:

  • 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
  • Enterprise AI use rose from 55% of organisations in 2023 to 88% in 2025, according to McKinsey’s Global Surveys on the State of AI.

A question worth separating out:

Q: What should teams do after an agent completes a sensitive action?

A: Teams should retain a full audit trail of the initiating employee, agent identity, machine account, policy decision, target tool, data touched, and result. That record supports incident review, compliance evidence, and internal accountability. Without it, organisations can see that an action happened but not who authorised it, which policy applied, or where control failed.

👉 Read our full editorial: Runtime authorisation must govern agentic AI decisions, not people


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.