<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Anish Bista</title><link>https://anishbista.org/tags/security/</link><description>Recent content in Security on Anish Bista</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://anishbista.org/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Treat Your AI Agent Like Untrusted Code: Sandboxing with Docker and Kubernetes</title><link>https://anishbista.org/blog/sandboxing-ai-agents/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid>https://anishbista.org/blog/sandboxing-ai-agents/</guid><description>&lt;p>Most of us have now run an AI agent that writes code and then runs it. Many of us did that on a laptop with cloud credentials in &lt;code>~/.aws&lt;/code>, an API token in the environment, and SSH keys in &lt;code>~/.ssh&lt;/code>.&lt;/p>
&lt;p>My argument in this post is simple: &lt;strong>an AI agent is a program whose exact actions you don’t write and can’t fully predict. You set the goal and the tools, and anything it reads can try to steer it. Treat it like untrusted code and put it in a box.&lt;/strong>&lt;/p></description></item></channel></rss>