
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Parminder Singh | Software Engineer &amp; Architect</title>
      <link>https://singhspeak.com/blog</link>
      <description>Thoughts on software development and life.</description>
      <language>en-us</language>
      <managingEditor>undefined (Parminder Singh)</managingEditor>
      <webMaster>undefined (Parminder Singh)</webMaster>
      <lastBuildDate>Tue, 21 Apr 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://singhspeak.com/tags/incident-response/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://singhspeak.com/blog/22-second-breach-windows-mean-ai-enforcement-must-be-inline</guid>
    <title>22-Second Breach Windows Mean Your AI Enforcement Must Be Inline</title>
    <link>https://singhspeak.com/blog/22-second-breach-windows-mean-ai-enforcement-must-be-inline</link>
    <description>Mandiant M-Trends 2026 reports that attack handoff time collapsed from 8 hours to 22 seconds. At that tempo, log-and-alert on AI traffic is structurally incapable of preventing damage. If your AI enforcement operates on a review cycle measured in minutes, the breach is complete before the first alert fires. AI traffic enforcement must be inline and synchronous.</description>
    <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
    <author>undefined (Parminder Singh)</author>
    <category>ai-security</category><category>ai-governance</category><category>agentic-ai</category><category>incident-response</category><category>real-time-enforcement</category>
  </item>

    </channel>
  </rss>
