<?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 Rishab Kumar</title>
    <link>https://rishabkumar.com/tags/security/</link>
    <description>Recent content in security on Rishab Kumar</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 02 Nov 2026 14:50:25 -0600</lastBuildDate><atom:link href="https://rishabkumar.com/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your AI Agent Doesn&#39;t Need Less Power. It Needs a Smaller Blast Radius.</title>
      <link>https://rishabkumar.com/blog/ai-agent-blast-radius/</link>
      <pubDate>Mon, 02 Nov 2026 14:50:25 -0600</pubDate>
      
      <guid>https://rishabkumar.com/blog/ai-agent-blast-radius/</guid>
      <description>Imagine giving an AI coding agent root access, Docker, and permission to run privileged containers, then telling it to destroy everything it can reach.
That is exactly what I did live on stage at WeAreDevelopers World Congress North America.
The agent succeeded. It deleted every container, image, volume, network, and build cache it could find.
My host machine was fine.
That result captures the main idea behind my talk, rm -rf: Horror Stories From Unsandboxed AI Agents (and How Docker Fixes This): the command did not become safe.</description>
    </item>
    
  </channel>
</rss>
