<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NIST CAISSI on CybersecurityOS</title><link>http://www.cybersecurityos.net/tags/nist-caissi/</link><description>Recent content in NIST CAISSI on CybersecurityOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 25 Oct 2026 15:01:26 +0000</lastBuildDate><atom:link href="http://www.cybersecurityos.net/tags/nist-caissi/index.xml" rel="self" type="application/rss+xml"/><item><title>When the Agent Is the Incident: NIST, NSA, and CISA's 10 Key Practices for SI Incident Response</title><link>http://www.cybersecurityos.net/posts/ai-devsecops/nist-cisa-nsa-si-incident-response-key-practices/</link><pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate><guid>http://www.cybersecurityos.net/posts/ai-devsecops/nist-cisa-nsa-si-incident-response-key-practices/</guid><description>&lt;p&gt;Every incident response playbook you&amp;rsquo;ve ever written assumes the same cast. There&amp;rsquo;s an attacker, there&amp;rsquo;s a target, and there&amp;rsquo;s you in between. On October 16, 2026, NIST, NSA, and CISA published guidance for an incident where that cast breaks down: the thing you&amp;rsquo;re responding to is the agent you deployed, doing something nobody told it to do.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the core idea in &lt;a href="https://www.nist.gov/news-events/news/2026/10/key-practices-incident-readiness-and-response-super-intelligence-training"&gt;Key Practices for Incident Readiness and Response in Super Intelligence Training and Evaluation&lt;/a&gt;. It&amp;rsquo;s voluntary, it&amp;rsquo;s 14 pages, and it&amp;rsquo;s the clearest statement yet from the U.S. government that agent misbehavior is an incident class of its own, not a footnote to prompt injection.&lt;/p&gt;</description></item></channel></rss>