Join our Newsletter — 33% off our NHI Course

What would it take for runtime action authorization to stand alone?

 

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

TL;DR: Agentic security needs separate reachability and execution controls, EnforceAuth argues, because identity governance can prove who may connect while runtime authorization decides whether a live action should execute. The control boundary has to sit on the decision object, not the login event.

Editorial analysis by NHI Mgmt Group, based on content published by EnforceAuth: “Two Authorization Planes: A Technical Comparison of Okta and the EnforceAuth AI Security Fabric”.

Key questions

Q: Why do agentic systems need more than role-based access control?

A: Role-based access control is too coarse when the actor can choose actions at runtime.

Q: What are the signs that identity governance is being asked to do runtime enforcement work?

A: A common sign is when audit evidence shows who authorised an agent and what it could access, but nothing shows whether the specific action was allowed at execution time.

Q: How should security teams separate AI agent access control from runtime action authorization?

A: Treat them as two different control planes.

Practitioner guidance

  • Define the decision object for each agent workflow Document whether the control point governs tool reachability, object relationships, or the action itself.
  • Separate delegation checks from execution checks Keep directory, token, and ownership controls in the identity layer, then add a distinct policy decision for request arguments, live state, and transaction rules.
  • Instrument decision evidence for high-risk actions Record the policy version, input context, and allow or deny outcome for transfers, writes, and cross-tenant operations so auditors can see the runtime verdict.

Bottom line: Agentic security cannot rely on a single authorisation layer because reachability and execution are different control problems.

Glossary terms: Decision Object, Runtime Action Authorization, Attribution, Policy decision point

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: 20712
 

Agentic authorisation now requires two distinct control planes: identity-layer governance answers reachability, while runtime authorization answers execution legitimacy. Those are different computations with different inputs, and teams that collapse them into one control create a blind spot around live business state. The practitioner implication is that agent governance must be designed as layered decisioning, not as a single entitlement check.

A few things that frame the scale:

  • Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.

A question worth separating out:

Q: What should organisations do when a valid agent identity can still trigger an invalid business action?

A: They should keep the identity layer for reachability and attribution, then place a separate policy decision in the execution path for the business rule itself. The key question is not whether the identity is authenticated, but whether the specific action is acceptable in context. If the answer depends on live state, identity controls alone are insufficient.

👉 Read our full editorial: Identity-layer control and runtime authorization for agentic systems



   
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.