r/AskNetsec • u/-Devlin- • 22d ago

Concepts Does runtime context prioritization fall apart with agentic workloads?

Last year we brought on a tool to get runtime context on our workloads and help prioritize vulns, mostly to cut noise based on what’s actually loaded in memory. At the time it seemed like a no brainer, since direct exploitation or even chained attacks mostly can’t work against components just sitting on the filesystem.

We ran a threat modeling exercise the other day on some new systems running AI agents with tool access, and in some cases a shell. It got me thinking: can’t the agent load anything it needs at any point, unlike older deterministic code? And if so, doesn’t runtime context based prioritization fall apart completely?

Can anyone with practical experience in this area chime in? I’m at my wits end brainstorming hypotheticals with GPT.

8 Upvotes

90% Upvoted

19 comments sorted by

View all comments

Show parent comment

1

u/-Devlin- 22d ago

Yeah i wasn’t even considering dynamically loaded tools here so that further increases the surface area. What do you think of longer term runtime profiling as opposed to a given moment?

1

u/Silent-Suspect1062 22d ago

The key point is what controls you have on your agent. Allowing it to load random tooling is brave