<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Breach-Containment on microsegment.io</title>
    <link>https://microsegment.io/tags/breach-containment/</link>
    <description>Recent content in Breach-Containment on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Oct 2026 09:55:01 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/breach-containment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Containment Signal: 2026-10-16</title>
      <link>https://microsegment.io/post/2026-10-16-containment-signal/</link>
      <pubDate>Fri, 16 Oct 2026 09:55:01 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-10-16-containment-signal/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Automated coverage digest, not an incident assessment.&lt;/strong&gt; This maps published RSS metadata to containment themes using explicit phrase rules. It does not establish that segmentation failed, would have stopped an attack, or replaces patching.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://microsegment.io/containment-signal-index/&#34;&gt;Explore the interactive index&lt;/a&gt; · &lt;a href=&#34;https://microsegment.io/containment-signal-index/data/2026-10-16.json&#34;&gt;Download this snapshot&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;todays-signal&#34;&gt;Today&amp;rsquo;s signal&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;OT &amp;amp; connected devices&lt;/strong&gt; has the largest weighted share (47.7%). The sample contains &lt;strong&gt;11 matched items&lt;/strong&gt;, published within the last 14 days. 11 items are newly observed by this monitor today, not necessarily newly published.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GPU Monitoring Needs Its Own Containment Boundary</title>
      <link>https://microsegment.io/post/2026-10-13-gpu-monitoring-needs-containment/</link>
      <pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-10-13-gpu-monitoring-needs-containment/</guid>
      <description>&lt;p&gt;The inference endpoint has authentication. The GPU cluster has tenant boundaries. The monitoring port is reachable from everywhere because someone needed to make the dashboard work.&lt;/p&gt;&#xA;&lt;p&gt;That is the deployment pattern I would challenge in the next containment review.&lt;/p&gt;&#xA;&lt;p&gt;Monitoring should be an explicit dependency, not an exception to segmentation.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-the-research-actually-shows&#34;&gt;What The Research Actually Shows&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://lava.security/research/cve-2026-47483-nvidia-dcgm-exporter-vulnerability&#34;&gt;Lava&amp;rsquo;s October 8 research&lt;/a&gt; reports approximately 2,100 hosts exposing DCGM Exporter telemetry without authentication across four scans between March and May 2026. The responses contained more than 12,000 unique GPU identifiers. Hardware details, utilization and workload labels could expose information about the infrastructure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>mTLS Is Not A Containment Policy</title>
      <link>https://microsegment.io/post/2026-10-06-mtls-is-not-a-containment-policy/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-10-06-mtls-is-not-a-containment-policy/</guid>
      <description>&lt;p&gt;The connection is encrypted. Both workloads have valid certificates. The dashboard is green.&lt;/p&gt;&#xA;&lt;p&gt;Now assume the calling workload is compromised. Which services can it still use?&lt;/p&gt;&#xA;&lt;p&gt;That is the containment question. A successful handshake is not the answer.&lt;/p&gt;&#xA;&lt;h2 id=&#34;identity-is-an-input-to-policy&#34;&gt;Identity Is An Input To Policy&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://csrc.nist.gov/pubs/sp/800/207/a/final&#34;&gt;NIST SP 800-207A&lt;/a&gt; describes cloud-native access control using application and service identities alongside network parameters and user identities. Its architectural direction is granular application access, not simply encrypted connectivity.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OT Integrator Access Needs An Expiry Date</title>
      <link>https://microsegment.io/post/2026-09-29-ot-integrator-access-needs-an-expiry-date/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-09-29-ot-integrator-access-needs-an-expiry-date/</guid>
      <description>&lt;p&gt;A supplier finishes a commissioning project. The plant accepts the work. What expires?&lt;/p&gt;&#xA;&lt;p&gt;The purchase order is not the security boundary. The useful questions are whether the support route still works, which assets it reaches, and what engineering material remains outside the plant.&lt;/p&gt;&#xA;&lt;p&gt;Those are separate problems. A network rule can close a connection. It cannot recall a copied drawing.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-evidence-engineering-knowledge-outside-the-plant&#34;&gt;The Evidence: Engineering Knowledge Outside The Plant&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://www.fbi.gov/investigate/cyber/alerts/2026/considerations-for-critical-infrastructure-operators-working-with-third-party-ics-integrators&#34;&gt;September 23 FBI/CISA fact sheet on third-party ICS integrators&lt;/a&gt; describes a March-April 2025 intrusion into a U.S. industrial automation company. Attackers searched for customer and SCADA material and assembled archives containing device information and schematics for presumed exfiltration.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Platform Was Not Breached. The Delegated Key Was.</title>
      <link>https://microsegment.io/post/2026-09-22-delegated-saas-key-containment/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-09-22-delegated-saas-key-containment/</guid>
      <description>&lt;p&gt;The SaaS platform can remain intact while a trusted application identity becomes the attack path.&lt;/p&gt;&#xA;&lt;p&gt;That is the important distinction in the recent BigCommerce and Ribon incident. &lt;a href=&#34;https://www.bleepingcomputer.com/news/security/bigcommerce-alerts-merchants-of-data-breach-linked-to-ribon-apps/&#34;&gt;BigCommerce told BleepingComputer&lt;/a&gt; that credentials belonging to the third-party Ribon and Ribon 1.5 applications were compromised. According to the statement, the credentials were used to inject malicious scripts into a small number of merchant storefronts. The reporting also says attackers accessed shopper data between September 13 and September 17, 2026.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Email Security Gateway Is Now An Attack Origin</title>
      <link>https://microsegment.io/post/2026-09-15-email-security-gateway-containment/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-09-15-email-security-gateway-containment/</guid>
      <description>&lt;p&gt;The system designed to inspect hostile email can itself become the first compromised workload.&lt;/p&gt;&#xA;&lt;p&gt;That is the uncomfortable lesson from &lt;a href=&#34;https://www.cisco.com/c/en/us/support/docs/csa/cisco-sa-esa-inj-2bLVGmhX.html&#34;&gt;Cisco Secure Email Gateway CVE-2026-76461&lt;/a&gt;. Cisco says insufficient validation in AsyncOS email parsing allows an unauthenticated remote attacker to send a crafted message, execute arbitrary SQL statements, and reach command execution with root privileges on the underlying operating system.&lt;/p&gt;&#xA;&lt;p&gt;Cisco published the critical advisory on September 14, 2026, assigned a CVSS score of 9.8, confirmed active exploitation, and provided fixed releases. There is no workaround. &lt;a href=&#34;https://www.cisa.gov/known-exploited-vulnerabilities-catalog&#34;&gt;CISA added the vulnerability to its Known Exploited Vulnerabilities catalog&lt;/a&gt;, according to the &lt;a href=&#34;https://www.cyber.gc.ca/en/alerts-advisories/cisco-security-advisory-av26-921&#34;&gt;Canadian Centre for Cyber Security advisory&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Your Microsegmentation Policy Is Not Proven Until You Test The Deny</title>
      <link>https://microsegment.io/post/2026-09-08-test-the-deny/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-09-08-test-the-deny/</guid>
      <description>&lt;p&gt;Most segmentation reviews prove that allowed traffic still works.&lt;/p&gt;&#xA;&lt;p&gt;The application opens. The database responds. Monitoring is green. The change ticket closes.&lt;/p&gt;&#xA;&lt;p&gt;None of that proves containment.&lt;/p&gt;&#xA;&lt;p&gt;Containment depends on the traffic that must &lt;strong&gt;not&lt;/strong&gt; work: the workstation that cannot reach the database, the web tier that cannot administer the hypervisor, the compromised build runner that cannot query production secrets, and the ransomware process that cannot discover every file server.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When The Network Infrastructure Lies</title>
      <link>https://microsegment.io/post/2026-09-01-when-network-infrastructure-lies/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-09-01-when-network-infrastructure-lies/</guid>
      <description>&lt;p&gt;Most security architectures assume the network will tell the truth.&lt;/p&gt;&#xA;&lt;p&gt;The router reports its configuration. TACACS records who administered it. Syslog preserves what changed. The monitoring platform shows which paths were active. During an incident, those records become the timeline.&lt;/p&gt;&#xA;&lt;p&gt;But what happens when the attacker controls the systems that create the evidence?&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.sygnia.co/blog/fire-ant-evolves-from-hypervisors-to-trusted-infrastructure/&#34;&gt;Sygnia&amp;rsquo;s August 2026 Fire Ant investigation&lt;/a&gt; describes a China-nexus actor compromising Cisco IOS XR routers, TACACS infrastructure, and Linux management hosts. The actor used routers for covert connectivity and traffic collection, intercepted administrative authentication, maintained persistent access, and manipulated logging and command output.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Login Worked. The Breach Did Not.</title>
      <link>https://microsegment.io/post/2026-08-25-the-login-worked-the-breach-did-not/</link>
      <pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-08-25-the-login-worked-the-breach-did-not/</guid>
      <description>&lt;p&gt;On August 22, 2026, a threat actor convinced a ReliaQuest employee to enter a password into a fake single sign-on page and approve an MFA push.&lt;/p&gt;&#xA;&lt;p&gt;The login worked.&lt;/p&gt;&#xA;&lt;p&gt;The attacker received a brief session on the identity dashboard. But the session had view-only access. Attempts to open applications were denied because the device did not meet ReliaQuest&amp;rsquo;s trust requirements. ReliaQuest then terminated the sessions, expired the password, and reset every authentication factor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The 2026 Forrester Wave For Microsegmentation: Why Illumio Stands Out</title>
      <link>https://microsegment.io/post/2026-08-22-forrester-wave-microsegmentation-2026-illumio/</link>
      <pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-08-22-forrester-wave-microsegmentation-2026-illumio/</guid>
      <description>&lt;p&gt;Forrester has published &lt;em&gt;The Forrester Wave™: Microsegmentation Solutions, Q3 2026&lt;/em&gt;, evaluating 10 vendors against 25 criteria.&lt;/p&gt;&#xA;&lt;p&gt;The headline for Illumio is strong: Forrester named it a Leader, Illumio received the highest overall scores of any evaluated vendor in both the Current Offering and Strategy categories, and it was designated a Customer Favorite based on customer feedback in the evaluation.&lt;/p&gt;&#xA;&lt;p&gt;That combination matters more than a Leader badge on its own.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
