Join our Newsletter — 33% off our NHI Course

What would it take for runtime authorisation to close the agentic AI gap?

 

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

TL;DR: Runtime authorisation now matters more than output moderation for agentic AI, EnforceAuth says, because autonomous systems can plan, decide, and execute at machine speed. Session-long authority makes periodic review too late to catch which actions were actually authorised.

Editorial analysis by NHI Mgmt Group, based on content published by EnforceAuth: “The AUTHOR Framework: Securing the Agentic Enterprise, One Action at a Time”.

Key questions

Q: Why do autonomous agents make traditional access reviews less effective?

A: Access reviews assume permissions persist long enough to be observed, challenged, and recertified.

Q: What are the signs that agentic AI controls are too weak?

A: The warning signs are capability exposure and late-stage detection.

Q: What breaks when AI assistants rely only on built-in safety filters?

A: Built-in safety filters fail when attackers use obfuscation, multi-turn escalation, or indirect prompt injection to change the model’s interpretation of allowed behaviour.

Practitioner guidance

  • Define the action boundary Map every tool call, API invocation, and workflow trigger that an autonomous system can execute, then require policy evaluation before any of them proceed.
  • Separate identity from authority Assign unique, revocable identities to agents and sub-agents, but do not assume identity assignment alone governs what the system may decide to do.
  • Add runtime decision controls Classify irreversible and high-consequence actions so they are intercepted for context, intent, and reversibility checks before execution.

Bottom line: Autonomous AI changes governance from access assignment to action authorization, which makes runtime controls more important than output moderation.

Glossary terms: Runtime Authorisation, Least Agency, Authorization Gap, Decision Receipt

Explore further

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


This topic was modified 6 days ago by NHI Mgmt Group

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

Runtime authorization is the missing control plane because autonomous systems turn every tool call into a governance decision. The article is right to separate AI safety from AI security. Once an agent can choose actions at runtime, policy has to sit on the execution path rather than around the model perimeter. Practitioners should stop treating prompts, outputs, and human review as substitutes for enforcement.

A few things that frame the scale:

  • 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
  • 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: Should organisations treat agent identity and runtime authority as the same control?

A: No. Agent identity tells you which actor is involved, but runtime authority decides whether a specific action should happen now. Identity assignment without action mediation leaves a gap between authentication and enforcement, which is where most agentic AI failures begin.

👉 Read our full editorial: Runtime authorization is the missing control plane for agentic AI



   
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.