<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Article on microsegment.io</title>
    <link>https://microsegment.io/categories/article/</link>
    <description>Recent content in Article on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/categories/article/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Management Consoles: The Keys to the Kingdom</title>
      <link>https://microsegment.io/post/2026-04-08-management-consoles-keys-to-the-kingdom/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-04-08-management-consoles-keys-to-the-kingdom/</guid>
      <description>&lt;h2 id=&#34;the-wrong-thing-is-still-trusted&#34;&gt;The Wrong Thing Is Still Trusted&lt;/h2&gt;&#xA;&lt;p&gt;Defenders keep hardening endpoints, tuning detections, and buying more visibility.&lt;/p&gt;&#xA;&lt;p&gt;Meanwhile, attackers keep going after the systems that already have permission to touch everything.&lt;/p&gt;&#xA;&lt;p&gt;That is the real problem with management consoles.&lt;/p&gt;&#xA;&lt;p&gt;When a laptop gets compromised, you have an incident.&lt;/p&gt;&#xA;&lt;p&gt;When a management console gets compromised, you may have a change-control&#xA;problem, an identity problem, a visibility problem, and a lateral movement&#xA;problem all at once.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hard Truths #2: Patching Is Whack-a-Mole, Not Strategy</title>
      <link>https://microsegment.io/post/2026-03-31-hard-truths-2-patching-whack-a-mole/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-03-31-hard-truths-2-patching-whack-a-mole/</guid>
      <description>&lt;h2 id=&#34;the-math-nobody-wants-to-do&#34;&gt;The Math Nobody Wants to Do&lt;/h2&gt;&#xA;&lt;p&gt;March Patch Tuesday: 84 vulnerabilities. Including two zero-days already under active exploitation.&lt;/p&gt;&#xA;&lt;p&gt;February: APT28 was exploiting CVE-2026-21513 in MSHTML &lt;strong&gt;before the patch even shipped&lt;/strong&gt;. A Russian state-sponsored group had your number before Microsoft did. &lt;a href=&#34;https://thehackernews.com/2026/03/apt28-tied-to-cve-2026-21513-mshtml-0.html&#34;&gt;Source&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Every month, the same ritual plays out across enterprise IT:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Vendor drops patches&lt;/li&gt;&#xA;&lt;li&gt;Security team triages&lt;/li&gt;&#xA;&lt;li&gt;Testing begins&lt;/li&gt;&#xA;&lt;li&gt;Change advisory boards convene&lt;/li&gt;&#xA;&lt;li&gt;Deployment rolls out in waves&lt;/li&gt;&#xA;&lt;li&gt;Stragglers get chased down&lt;/li&gt;&#xA;&lt;li&gt;Next Patch Tuesday arrives&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Repeat forever.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hard Truths #1: Your Security Tools Are the Attack Surface</title>
      <link>https://microsegment.io/post/2026-03-26-hard-truths-1-security-tools-attack-surface/</link>
      <pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-03-26-hard-truths-1-security-tools-attack-surface/</guid>
      <description>&lt;h2 id=&#34;the-pattern-nobody-wants-to-see&#34;&gt;The Pattern Nobody Wants to See&lt;/h2&gt;&#xA;&lt;p&gt;This month alone, four major security vendors had their management infrastructure turned into attack vectors. Not the endpoints they protect. The management consoles that control them.&lt;/p&gt;&#xA;&lt;p&gt;Let that sink in.&lt;/p&gt;&#xA;&lt;h3 id=&#34;the-incidents&#34;&gt;The Incidents&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;Cisco Secure Firewall Management Center&lt;/strong&gt; - CVE-2026-20131, CVSS 10.0. Unauthenticated remote code execution as root. The Interlock ransomware group exploited this as a zero-day for &lt;strong&gt;36 days&lt;/strong&gt; before Cisco even disclosed it. Amazon&amp;rsquo;s threat intelligence team caught them exploiting it since January 26. The attackers had custom RATs, recon scripts, proxy infrastructure - the full playbook. All through a firewall management console.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microservices and Microsegmentation</title>
      <link>https://microsegment.io/post/2019-09-16-microservices-and-microsegmentation/</link>
      <pubDate>Mon, 16 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-09-16-microservices-and-microsegmentation/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;The thing to remember is that just because dev has decided to leverage&#xA;microservices does not in turn mean that the network somehow magically becomes&#xA;microsegmented or that if microsegmentation is used to optimize the network&#xA;service architecture that suddenly apps become microservices. Microsegmentation&#xA;can be used to logically isolate monolithic applications as easily as it can&#xA;microservices.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://dzone.com/articles/microservices-versus-microsegmentation&#34;&gt;Article from DZone&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&amp;ldquo;Micro is big these days&amp;rdquo; - The below statement is from an article showing the&#xA;similarities and differences between microservices and microsegmentation. Of&#xA;course we all know the differences, but we might have never thought about the&#xA;similarities between the two approaches.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
