Join our Newsletter — 33% off our NHI Course

Why does delegated AI authority create Lethal Trifecta risk?

 

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

TL;DR: AI agents carried the lethal trifecta in 98% of 100 production cases, with DTEX saying only 11% met baseline security expectations. Delegated workflows need tighter prevention and attribution, or untrusted content can drive action through broad access.

Editorial analysis by NHI Mgmt Group, based on content published by DTEX: “98% of AI Agents Are Living in the Lethal Trifecta. Here’s What That Means for Insider Risk”.

By the numbers:

  • 98% of the agents evaluated had simultaneous access to private data, exposure to untrusted external content, and the ability to take outbound action.
  • Only 11% of the agents assessed passed a baseline security benchmark.
  • 40% of the population studied were exposed giants but accounted for 60% of the aggregate risk.

Key questions

Q: Why does delegated AI activity create insider risk instead of only model risk?

A: Because the agent is acting on behalf of a user or workflow, the key question becomes who moved the data and whether that action was authorised.

Q: What are the signs that AI agent risk is being underestimated?

A: The clearest signs are self-serve deployment, strong claims about security without independent testing, and broad access that exceeds the user’s normal task scope.

Q: What breaks when AI agents can read data, ingest untrusted content, and communicate externally in one workflow?

A: The control boundary breaks because the agent can turn malicious content into action while still holding delegated access to sensitive data.

Practitioner guidance

  • Map every agent workflow that combines reading, tool use, and outbound communication Identify where an agent can access private data, ingest untrusted content, and transmit externally in the same task chain, then classify the workflow by exposure level.
  • Separate prevention controls from logging controls Test whether the environment can block unsafe tool calls or outbound movement before execution, rather than relying on audit logs to reconstruct a completed action.
  • Limit delegated access to task-scoped authority Remove standing permission where the agent does not need persistent access, and require explicit policy evaluation at the action level for sensitive operations.

Bottom line: AI agents are already operating with a combination of data access, untrusted input, and outbound reach that creates insider-risk conditions, not theoretical future exposure.

Glossary terms: Lethal Trifecta, Exposed Giants, Delegated Authority Model, Attribution gap

Explore further

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


This topic was modified 7 days ago by NHI Mgmt Group

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

Delegated AI has become an insider-risk boundary, not just an application-safety boundary: once an agent can act on behalf of a user, the governance question changes from model behaviour to delegated authority. The article’s core signal is that security teams are already operating in an environment where the agent, not the human, is the active mover of data. That means insider-risk programmes must treat agent activity as part of the identity perimeter, not as a separate AI concern. The practical conclusion is that attribution and policy enforcement must follow the delegated actor, not only the user who enabled it.

A few things that frame the scale:

  • Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: Should organisations prioritise fewer agents or tighter controls first?

A: Tighter controls should come first for the highest-capability agents, because risk concentrates where utility and privilege are both high. Reducing the number of agents helps only if it changes access breadth, tool permissions, and attribution quality. Otherwise, the same exposure simply moves elsewhere.

👉 Read our full editorial: AI agents’ default trifecta creates a baseline insider-risk problem


This post was modified 7 days 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.