Replies: 1 comment
|
Data leaving is still the one people worry about most, and it's usually a credential the agent had legit access to going somewhere it shouldn't. Destructive changes come up less in issues, mostly because people already keep agents off anything they can't undo. On controls vs proof, people want both, and they ask for them in that order. Block the obvious stuff first, then have a record they can hand to someone else when something does get through. Most of the hard problems end up being about the traffic that doesn't go through the proxy at all, which is why containment matters as much as the scanning. Good luck with the research. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Josh and everyone, I'm doing early research on agents that make real tool calls (I'm exploring building in this space) and wanted to ask the people closest to it.
Pipelock started from exfiltration and egress, and it now signs receipts for boundary decisions. I'm curious how that lines up with what users are actually worried about:
Thanks for building this in the open.
All reactions