Urgent.News

What's breaking now, across thousands of outlets.

AI

How Do You Threat-Model an Application That Uses Autonomous AI Agents?

You spent years building a threat model you trust. You know your trust boundaries, you've mapped your data flows, and your team can recite STRIDE in their sleep. Then someone shipped an autonomous AI agent into the product, and quietly, every assumption underneath that model cracked. Here's the problem in one sentence: traditional software does what you programmed it to do, but an autonomous…

Traditional software follows the code you give it, but autonomous AI agents act on what they believe, which is a different risk. These agents read customer emails, query databases, call APIs, and write files - all based on untrusted input. The tricky part is that the input and instructions are both just text, with no clear separation.

Prompt injection is the new SQL injection - untrusted text can become a command when ingested by the agent. This changes the focus from stopping bad input to limiting the damage if it happens. Traditional threat modeling frameworks like STRIDE can still apply, but you need to redraw the boundaries to include the agent, its tools, and its memory as first-class assets with their own trust boundaries.

Consider spoofing (untrusted content impersonating system instructions), tampering (injecting changes through data inputs), repudiation (lack of proof of what the agent was told and why it acted), information disclosure (data exfiltration via injected instructions), denial of service (agents looping and exhausting resources), and elevation of privilege (agents gaining excessive permissions through successful injections).

The biggest threat is data exfiltration through injected instructions, but other risks like unbounded tool usage and over-provisioned agent permissions also matter. The key is to treat each tool the agent uses as if it could be abused by an attacker, granting only the least privilege necessary.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

I finally cut AI context bloat by 80% and the fix was embarrassingly simple

A few months ago I watched an agent do something deeply cursed. It had already fetched the data. It had already parsed the data. It had already stored the useful fields.

  • AI agents previously included entire raw tool responses in subsequent model calls
  • Solution was to store full results in structured state outside the model
  • This change improved agent quality and efficiency significantly

Artificial intelligence created an attack for Chrome in six days

Researchers at security firm XBOW used an AI model to build a full-chain Google Chrome exploit combining three unknown bugs in six days.

  • Researchers at XBOW created Chrome exploit in six days using AI
  • AI performed source code analysis, testing, and initial exploit creation
  • Exploit affects Windows users, no user interaction needed

More from Wednesday 14 October →