Agent security and risk
How to run agents safely: a sandbox rather than a hook, scoped and reversible automation, and compliance in regulated companies.
- 6 posts, newest first
- A hook is not a boundary: why agents need a sandbox A training group got an agent past a hook that guarded a secrets file. A hook filters the calls it was written for, a sandbox limits what the agent can reach, and the trade between the two is a company decision.
- In a regulated enterprise, the committee is the AI bottleneck Code generation is solved. In a regulated enterprise the constraint is the approval process, so the fastest path to adoption is one that needs no new tool approved.
- Every automation needs a scoped, reversible sandbox Teams design what their automations do and neglect where they run. A written blast radius, a narrow scope and throwaway environments decide whether you can leave an automation unattended.
- Vouch for the harness, not for its output Code review cannot keep up with agent output. Open source maintainers already admit contributors instead of reviewing contributions, and in an agentic factory the contributor to admit is the harness.
- A vibecoded SaaS leaked user data because nobody owned the design A production SaaS built by vibe coding failed in four different ways with one root cause. What survived shows why AI-generated code needs someone who owns the system design.
- Well-built agents close compliance gaps that manual processes leave Compliance teams block agents as too risky while manual processes run on memory and reconstructed logs. Properly architected agents make audit trails and enforcement automatic.