Join our Newsletter — 33% off our NHI Course

Will runtime authorisation stop AI agent governance from missing exposure?

 

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

TL;DR: PlainID's analysis of a contract assistant with an app registration, owner field and quarterly certification finds it still exposed a draft acquisition agreement because governance never checked access at request time. Practitioners need runtime authorization to decide before the agent reaches sensitive data, or review records remain documentary.

Editorial analysis by NHI Mgmt Group, based on content published by PlainID: “AI Agent Identity Governance: How to Control Agents Before They Touch Sensitive Data”.

By the numbers:

Key questions

Q: Why do AI agents create more governance risk than ordinary integrations?

A: AI agents can connect quickly, run continuously, and accumulate broad permissions across multiple services.

Q: How can security teams tell whether AI agent approval controls are actually working?

A: Look for evidence that sensitive actions trigger a fresh approval event, that approvals are tied to a specific human principal, and that the agent cannot proceed when the checkpoint fails.

Q: What breaks when AI agents are certified like human accounts?

A: Quarterly certification assumes the reviewer can judge whether an entitlement still matches a stable job, manager and workflow.

Practitioner guidance

  • Discover every live agent Inventory agents across identity providers, orchestration frameworks, MCP servers and cloud AI platforms, then record the business owner, function, environment and approved data categories.
  • Replace role grants with category scope Approve agent access in terms of business data and tool categories such as vendor contracts, procurement policies or M&A material, not broad roles or generic entitlements.
  • Bind the user to the agent decision Evaluate the human requester, the agent identity and the task together so a low-privilege user cannot reach restricted material through a powerful assistant.

Bottom line: AI agent governance fails when identity records and certification logs are treated as proof of control without request-time enforcement.

Glossary terms: AI Agent Identity Governance, Runtime Authorisation, Category-Based Scope, Integration Window Exposure

What's in the full article

PlainID's full analysis covers the operational detail this post intentionally leaves for the source:

  • Five-step governance model for AI agents from discovery through retirement
  • How runtime authorization differs from static identity certification in practice
  • Policy patterns for classifying data, tools and prompts into business categories
  • Evidence and audit considerations for proving agent decisions to regulators

👉 Read PlainID's analysis of AI agent identity governance and runtime access control →

Explore further

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


This topic was modified 1 week ago 2 times by NHI Mgmt Group

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

Paper governance is not governance for AI agents: An agent can carry an identity record, an owner and a certification result and still be unsafe if no control evaluates the request at the moment of access. That is the governance failure this example exposes. The programme described the agent correctly, but it did not govern the data path. The practitioner lesson is that identity evidence must be joined to runtime decisioning or it only creates audit comfort.

A few things that frame the scale:

  • 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
  • Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.

A question worth separating out:

Q: Should AI agent governance sit in IAM, IGA or runtime authorization?

A: It has to span all three, but the decisive control is runtime authorization. IAM creates the identity, IGA records who answers for it and what it is supposed to do, and runtime policy decides whether a specific request can proceed. Without that last layer, the programme remains documentary rather than preventive.

👉 Read our full editorial: AI agent identity governance fails when approval outruns runtime access


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.