Join our Newsletter — 33% off our NHI Course

Did 10 attacks show classical IAM fails for agentic AI?

 

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

TL;DR: 10 attack patterns show classical IAM cannot govern agent tool decisions after login, from VotalAI's case work. Runtime authorisation needs to follow each tool call, or identity, delegation and argument scope stay out of view.

Editorial analysis by NHI Mgmt Group, based on content published by VotalAI: “Why Your Agents Need a Different Auth Model: 10 Attacks That Break Classical IAM”.

Key questions

Q: Why do sub-agents increase the risk of privilege escalation?

A: Sub-agents increase risk when they inherit the orchestrator's credential or scope, because downstream tools cannot tell which worker actually asked for the action.

Q: How do security teams stop replay attacks against agent tool calls?

A: They should treat each sensitive tool call as a one-time capability, not a reusable session event.

Q: What breaks when AI authorization happens only at login?

A: A login-only model assumes the session stays safe after authentication, but AI systems may make many later decisions and tool calls across multiple services.

Practitioner guidance

  • Define action-level authorisation for every high-risk tool Require the runtime to evaluate each proposed call against the specific tool, resource and arguments before execution, rather than inheriting user-level access from the session.
  • Assign separate identities to every sub-agent Mint distinct credentials for each worker and bind parent-child delegation so one agent cannot silently expand another agent's access scope.
  • Use single-use capabilities for sensitive tool calls Treat replay resistance as part of authorisation design by issuing short-lived, one-time tokens for actions such as sending mail, moving money or reading scoped records.

Bottom line: Agentic systems break the classical assumption that authentication at the edge is enough to govern downstream action.

Glossary terms: Agent Identity, Decision-level Authorisation, Capability-Based Access Control, Delegation Chain

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

Classical IAM is the wrong abstraction for agent decisions: It was built to answer whether a principal may access a resource, not whether a runtime model may choose to act. In agentic systems, the important question is no longer who logged in, but what the agent decided to do with each tool call. That means edge-only authorisation leaves the real risk ungoverned, because the decision point has moved inside the workflow. The practitioner conclusion is that identity policy has to attach to actions, not just sessions.

A few things that frame the scale:

  • A Harris Poll survey of more than 300 technology decision-makers found that 86% expect agentic AI to deliver positive ROI, yet fewer than half had AI governance policies in place.

A question worth separating out:

Q: What should organisations log to make agent actions auditable?

A: They should log the complete delegation context for every verify, including the originating user, the agent identity, any parent agent, the tool requested, the target resource and the final decision. Without that tuple, audit trails show that a token was valid but not who actually drove the risky action.

👉 Read our full editorial: Why classical IAM breaks for agentic AI tool decisions


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.