<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aws on microsegment.io</title>
    <link>https://microsegment.io/tags/aws/</link>
    <description>Recent content in Aws on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Quarantine Must Stop Existing Connections</title>
      <link>https://microsegment.io/post/2026-10-20-quarantine-must-stop-existing-connections/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-10-20-quarantine-must-stop-existing-connections/</guid>
      <description>&lt;p&gt;The incident responder clicks quarantine. A fresh connection test fails. The ticket says contained.&lt;/p&gt;&#xA;&lt;p&gt;What happened to the connection that was already open?&lt;/p&gt;&#xA;&lt;p&gt;That is the next test I would add to a microsegmentation response exercise. Not another port scan. A live, harmless application exchange that starts before isolation and is observed throughout the change.&lt;/p&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;https://microsegment.io/post/2026-10-06-mtls-is-not-a-containment-policy/&#34;&gt;the earlier mTLS article&lt;/a&gt;, I touched on existing sessions. They deserve their own runbook. A policy change and a session termination are different events.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
