logoalt Hacker News

fennecbutt • yesterday at 9:40 PM • 7 replies • view on HN

I've been using iron proxy recently for a project I just started, it does network restrictions by domain etc with plenty of options, credential swapping and more.

I have no affiliation with it, but it solved most of what I need in one go when I was stressing out about it.

Only real problem remaining if you truly want to be able to trust agents is how to prevent data (in my case codebases the agent works on) exfiltration a la HF incident.

We can restrict network to trusted domains, but there's always a chance an agent could be extra slippery especially if prompt injected and doing something like pushing data out a few characters at a time.

In my case I'm also giving it gh access and having to deeply check things like: can it manage to fork public repos and embarrass us by submitting prs, could it open issues, etc.

But that's kind of solved by proxying the heck out of gh rather than giving it direct (or wrapping it or whatever) for additional controls that gh themselves don't provide.

I'm still musing over the "it could send data to an allowed domain in a way we don't expect that exfiltrates something"...


Replies

skybrian • yesterday at 10:59 PM

It seems like some kind of network logging would be useful? Even if you don't catch it, you'd want to know what it did.

➕ show 2 replies
igorhvr • today at 12:45 AM

I think matchlock ( https://github.com/jingkaihe/matchlock ) is the right design for this context (at least for secrets and keys) - a combination of virtual machines (not just containers, it is built on top of firecracker) with credential swapping just like iron proxy - the agents do not have access to the secrets at all but they receive placeholders instead and their network calls are intercepted and secrets are injected when the network requests happen... still does not solve the exfiltration problem you mentioned, though.

Aeroi • today at 12:09 AM

what about using a small decision model as anomaly detection or scanner. something like mouse-1.

➕ show 1 reply
iJohnDoe • today at 1:39 AM

Could you share a bit about what you’re working on that requires a swarm of agents working so autonomously that you even need to worry about them making a public fork?

sy135673 • today at 3:21 AM

[flagged]

macro8n • today at 3:40 AM

[flagged]

ghostlyInc • yesterday at 10:55 PM

[flagged]