Of all the problems in agent security, sandboxing solves the easiest problem.
751 karma · joined February 18, 2015
Of all the problems in agent security, sandboxing solves the easiest problem.
> if it's not okay for the agent to know the API key permanently, why is it okay for the agent to have one-off use of something that requires the same key?
Read commands vs. write commands. I'm okay having the agent fetch info for me, but I want to approve any state changes.
I do wonder what happens when everyone is using agents for this, though. If AI produces the text and AI also reads the text, then do we even need the intermediary at all?
It makes sense that SAST is better for the provided task. The CWE Top 25 seem like issues focused around patterns. Each one has a strictly enumerated set of vulnerable patterns that you can scan for, and then, the tool's task becomes simply finding an exploitable path to that pattern. This lends itself towards static methods. Every known weakness of LLMs, like hallucinations, needle-in-haystack, and context overflow, show up in this taint-analysis issue.
I also think this is why SAST did much better in Java. Pattern-based vulns + static languages make static taint analysis really powerful. LLMs have no advantage here, while all of their disadvantages are highlighted.
This article doesn't go into issues that LLMs are able to find that traditional SAST isn't. Auth vulnerabilities, for example - privilege escalation is a software pattern but not a code one, and it takes reasoning to build a permissions model and then test it for breaches. Business logic issues are other: ways users can get around usage limits, or get access to premium features or private data.
The blocker to this has always been the government refusing to reform. I don't see how increased exchange changes this. If anything, the Cuban government would've blocked any integration that threatens their control.
As an aside, the Scythians were not in what we'd today consider Persia (Iran). They originated around the north coast of the Black Sea, and extended east and southeast from there along the Eurasian steppe.
What sort of projects have you been able to work on? What's the work culture like? Do you find the actual technical problems you work on exciting, or is it more the domain that excites you (i.e. building and operating a racecar)?
Otherwise, I think becoming a billionaire while purely working on software is extremely unlikely, bordering on impossible. Billion-dollar net worths necessitate leading billion-dollar businesses, and those aren't made solely with code.
However, in many other fields, like consulting, or investment banking, or law school admissions, there isn't a similar quality of measurability. Indeed, for many of these fields, the signalling is the end in and of itself, where the job itself doesn't require specific skills, but it's a benefit to the hiring institution to hire from signalling institutions). These sort of problems are uniquely resistant to market mechanisms and need top-down reform.