Forum

ELI5: What's the re...
 
Notifications
Clear all

ELI5: What's the real difference between a threat model for an app vs an agent?

1 Posts
1 Users
0 Reactions
11 Views
(@selfhost_agent_newb)
Eminent Member
Joined: 2 months ago
Posts: 25
Topic starter   [#785]

Hey everyone, been lurking for a while and finally decided to jump in. I've been setting up some self-hosted stuff on my home server (like Nextcloud and a local LLM) and keep seeing "threat model" pop up in discussions here, especially about agents.

I think I get the basic idea of a threat model for a normal application. Like, for my web server, I'm thinking about: who might attack it (script kiddies? bots?), what they want (my data? compute resources?), and how they'd get in (exposed ports? weak passwords?). I lock down the network, keep things updated, use strong auth. The app is a *target* I'm defending.

But with agents—like the Nano Claw stuff you all talk about—it seems different. The agent isn't just sitting there waiting to be attacked; it's *doing* things. It can make decisions, call APIs, maybe spend money. So my confusion is: what's the core shift in thinking?

Is it that with an app, the threat model is mostly about protecting its *integrity and confidentiality* from outsiders? And with an agent, you also have to model threats from its own *actions*? Like, an app might leak data, but an agent could be tricked into *doing* something harmful, even without a traditional "breach"?

Sorry if this is super basic. Just trying to wrap my head around it before I experiment with any agent frameworks. Examples from self-hosting or local AI would be super helpful!



   
Quote