<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Market Overview on microsegment.io</title>
    <link>https://microsegment.io/post/</link>
    <description>Recent content in Market Overview on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Weekly Security Landscape: April 4 - 10, 2026</title>
      <link>https://microsegment.io/post/2026-04-10-weekly-security-landscape-w15/</link>
      <pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-04-10-weekly-security-landscape-w15/</guid>
      <description>&lt;h2 id=&#34;the-week-at-a-glance&#34;&gt;The Week at a Glance&lt;/h2&gt;&#xA;&lt;p&gt;This week was not really about malware. It was about trust boundaries failing in quiet, high-leverage places.&lt;/p&gt;&#xA;&lt;p&gt;Older routers became token theft infrastructure. Helpdesks and BPOs became initial access. Mobile and endpoint management platforms kept showing up in CISA KEV. AI kept compressing the window between disclosure and weaponization. And all of it pointed to the same uncomfortable truth: the highest-risk systems are often the ones defenders still treat as support plumbing.&lt;/p&gt;</description>
    </item>
    <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>Introducing the Blast Radius Calculator</title>
      <link>https://microsegment.io/post/2026-04-07-blast-radius-calculator/</link>
      <pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-04-07-blast-radius-calculator/</guid>
      <description>&lt;h2 id=&#34;why-blast-radius-matters&#34;&gt;Why Blast Radius Matters&lt;/h2&gt;&#xA;&lt;p&gt;When an attacker compromises a single workload, the real question isn&amp;rsquo;t &lt;em&gt;if&lt;/em&gt; they can move laterally &amp;ndash; it&amp;rsquo;s &lt;em&gt;how far&lt;/em&gt; they can go. In a flat network with no segmentation, the answer is: everywhere. Every reachable host becomes a stepping stone toward high-value assets like domain controllers, databases, ERP systems, and backup servers.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Blast radius&lt;/strong&gt; is the total number of workloads, services, and data stores an attacker can reach from an initial point of compromise. It&amp;rsquo;s the single most important metric for understanding the actual impact of a breach &amp;ndash; and the one most organizations can&amp;rsquo;t quantify.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Weekly Security Landscape: March 28 - April 3, 2026</title>
      <link>https://microsegment.io/post/2026-04-03-weekly-security-landscape-w14/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-04-03-weekly-security-landscape-w14/</guid>
      <description>&lt;h2 id=&#34;the-week-at-a-glance&#34;&gt;The Week at a Glance&lt;/h2&gt;&#xA;&lt;p&gt;This was the week supply chain attacks went industrial, management plane vulnerabilities kept stacking up, and AI proved it can write kernel exploits faster than most organizations can triage a CVE. Here&amp;rsquo;s what happened - and what it means for your architecture.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;-critical-teampcp-supply-chain-campaign-expands&#34;&gt;🔴 Critical: TeamPCP Supply Chain Campaign Expands&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;The biggest story of the month continued to grow.&lt;/strong&gt; TeamPCP&amp;rsquo;s supply chain attack, which started with compromising Aqua Security&amp;rsquo;s Trivy vulnerability scanner via GitHub Actions, expanded to hit LiteLLM (95 million PyPI downloads/month), Checkmarx KICS, and the Axios npm package (100 million weekly downloads).&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>M-Trends 2025: Unpacking the Threats and Why Microsegmentation is Your Strongest Defense</title>
      <link>https://microsegment.io/post/2025-05-20-m-trends-2025-analysis-the-power-of-microsegmentation/</link>
      <pubDate>Tue, 20 May 2025 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2025-05-20-m-trends-2025-analysis-the-power-of-microsegmentation/</guid>
      <description>&lt;h2 id=&#34;m-trends-2025-unpacking-the-threats-and-why-microsegmentation-is-your-strongest-defense&#34;&gt;M-Trends 2025: Unpacking the Threats and Why Microsegmentation is Your Strongest Defense&lt;/h2&gt;&#xA;&lt;p&gt;The recently released Mandiant M-Trends 2025 report offers a insightful look into the evolving cybersecurity landscape. As we digest its key findings, one thing becomes abundantly clear: attackers are becoming more opportunistic and sophisticated, exploiting any weakness they can find. For those of us focused on building resilient security architectures, the report underscores the importance of granular control and containment – principles at the heart of microsegmentation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Attackers think in graphs</title>
      <link>https://microsegment.io/post/2025-05-14-attackers-think-in-graphs/</link>
      <pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2025-05-14-attackers-think-in-graphs/</guid>
      <description>&lt;p&gt;&lt;strong&gt;The Graph Advantage: Why Attackers Think in Networks While Defenders Think in Rows&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;When a security analyst opens their SIEM dashboard, they typically see what defenders have seen for decades: endless tables of logs, sorted by timestamp, filtered by IP address, grouped by event type. Meanwhile, somewhere in the digital shadows, an attacker is mapping out their target&amp;rsquo;s infrastructure like a cartographer charting new territory—not in rows and columns, but as an interconnected web of relationships, vulnerabilities, and opportunities.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Recommended reading: Cyber Resilience: A Perishable Skill That Needs Practice</title>
      <link>https://microsegment.io/post/2025-04-22-recommended-reading-cyber-resilience/</link>
      <pubDate>Mon, 21 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2025-04-22-recommended-reading-cyber-resilience/</guid>
      <description>&lt;h1 id=&#34;recommended-reading-cyber-resilience-a-perishable-skill-that-needs-practice&#34;&gt;Recommended Reading: Cyber Resilience: A Perishable Skill That Needs Practice&lt;/h1&gt;&#xA;&lt;p&gt;Great &lt;a href=&#34;https://www.linkedin.com/pulse/cyber-resilience-perishable-skill-needs-practice-prof-dan-haagman-3kfvc/&#34;&gt;piece on LinkedIn&lt;/a&gt; by &lt;a href=&#34;https://www.linkedin.com/in/danhaagman/&#34;&gt;Prof. Dan Haagman&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;p&gt;Cyber resilience is like going to the gym: skip your workouts and you&amp;rsquo;ll get flabby fast. His big insight? Even seasoned execs throw out the playbook under pressure and just wing it.&lt;/p&gt;&#xA;&lt;p&gt;The fix? Get those tabletop exercises scheduled and keep adversary sims running. Your DR plan from 2015 won&amp;rsquo;t cut it against modern ransomware. Building muscle memory through practice is what separates the pros from the panicked.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The microsegmentation landscape in 2025</title>
      <link>https://microsegment.io/2025/04/17/the-state-of-microsegmentation-in-2025/</link>
      <pubDate>Thu, 17 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2025/04/17/the-state-of-microsegmentation-in-2025/</guid>
      <description>&lt;h1 id=&#34;the-microsegmentation-landscape-in-2025-current-state-and-future-directions&#34;&gt;The Microsegmentation Landscape in 2025: Current State and Future Directions&lt;/h1&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Microsegmentation has evolved significantly since its early days as a network security approach, becoming a cornerstone of modern zero trust security architectures. As we move through 2025, the microsegmentation landscape continues to mature with new technologies, integration capabilities, and use cases expanding beyond traditional data center environments. This overview examines the current state of microsegmentation, key trends, leading vendors, and future directions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Thoughts on the Attack matrix for Kubernetes</title>
      <link>https://microsegment.io/2020/04/14/thoughts-on-the-attack-matrix-for-kubernetes/</link>
      <pubDate>Tue, 14 Apr 2020 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2020/04/14/thoughts-on-the-attack-matrix-for-kubernetes/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;In a recent blog post Yossi Weizman talks about the &lt;a href=&#34;https://www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/&#34;&gt;Attack matrix for&#xA;Kubernetes&lt;/a&gt;&#xA;and i had a couple of thoughts about it. As Yossi rightly says, Kubernetes is&#xA;becoming a vital part in the compute stack of many companies. What i hear in my&#xA;network and during sessions with IT security teams is that they face new&#xA;challenges with Kubernetes-based orchestration platforms. The container&#xA;platforms are also perceived like a black box for traditional networking and IT&#xA;security folks, so it makes sense to understand the security risks that are&#xA;inherent to those platforms first.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Service Mesh</title>
      <link>https://microsegment.io/post/2019-11-23-the-service-mesh/</link>
      <pubDate>Sat, 23 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-11-23-the-service-mesh/</guid>
      <description>&lt;p&gt;Whenever you hear people speak about containers and container networking, there&#xA;is a high chance of the Service Mesh coming up as a topic. It is a real hype&#xA;and while being on the twitters i discovered this great article by &lt;a href=&#34;https://twitter.com/wm&#34;&gt;William Morgan&lt;/a&gt; of &lt;a href=&#34;https://buoyant.io&#34;&gt;@BuoyantIO&lt;/a&gt;, the creator of Linkerd.&lt;/p&gt;&#xA;&lt;p&gt;William does a great job of explaining the technology, the use cases, what to&#xA;use it for and what not and i have a couple of comments to add:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mitre ATT&amp;CK and Segmentation</title>
      <link>https://microsegment.io/post/2019-11-08-mitre-attack-and-segmentation/</link>
      <pubDate>Fri, 08 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-11-08-mitre-attack-and-segmentation/</guid>
      <description>&lt;p&gt;When people think about their strategic IT security projects, they often&#xA;think of the last incident they were affected of and try to mitigate that,&#xA;often by using technology only.&lt;/p&gt;&#xA;&lt;p&gt;This is a valid approach and probably is not so wrong, because we often&#xA;see waves of incidents rolling in, the wannacry wave, other ransomware&#xA;waves, certain exploit kits or malware waves. So it makes some sense&#xA;to concentrate on those threats when they happen. Of course you should&#xA;have done something long before it hit you or other people, but the&#xA;nature of IT security is that this hardly ever happens.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The importance of outbound policy</title>
      <link>https://microsegment.io/post/2019-11-05-the-importance-of-being-ehm-outbound-policy/</link>
      <pubDate>Tue, 05 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-11-05-the-importance-of-being-ehm-outbound-policy/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/William_Cheswick&#34;&gt;Bill Cheswick&lt;/a&gt;, a pioneer&#xA;in internet firewalls got, besides establishing what we today know as the&#xA;perimeter firewall, famous for the below quote to describe his ideas on&#xA;perimeter firewalls:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;A sort of crunchy shell around a soft, chewy center.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;The quote and metaphor is still used a lot by security professionals around&#xA;the world, to describe the state of the internal network &lt;strong&gt;behind&lt;/strong&gt; the perimeter&#xA;firewall.&lt;/p&gt;&#xA;&lt;p&gt;A crunchy shell in the 1990s was exactly the thing you needed to be more secure&#xA;from the threats found at that time. A lot of it was attacks against servers,&#xA;buffer and heap overflows on services directly exposed to the internet when not&#xA;consumed directly from the internet.&#xA;People could easily DoS or even better, hack, those services. Exposed sendmail&#xA;servers been a huge target at that time. Everything was exposed and routed, it is&#xA;hard to imagine today. The perimeter firewall did a great job and shielded the&#xA;vulnerable services from the evil internet and helped to secure them from the&#xA;outside world. The internet grew exponentially and threats changed quite&#xA;significantly and we all know that most threats today focus on endpoints rather&#xA;than datacenter services as a entry vector.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Implementing Sensible Network Segmentation</title>
      <link>https://microsegment.io/post/2019-10-18-podcast-implementing-sensible-network-segmentation/</link>
      <pubDate>Fri, 18 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-10-18-podcast-implementing-sensible-network-segmentation/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://packetpushers.net/podcast/tech-bytes-implementing-sensible-network-segmentation-with-tufin-sponsored/&#34;&gt;Packet Pushers Tech Bytes about Network Segmentation with&#xA;Tufin&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;A new week, a new Tech Bytes Packet Pushers podcast. This time Tufin markets&#xA;their policy management, which was a interesting show, but i have some comments.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;i think it&amp;rsquo;s a valid point to say that automated firewall policy management&#xA;can make a business more agile, especially considering how long the change&#xA;process normally takes and how we do it today&lt;/li&gt;&#xA;&lt;li&gt;the whole point about understanding the topology sounds like this is really&#xA;very slow to implement&lt;/li&gt;&#xA;&lt;li&gt;it&amp;rsquo;s hard to get any visibility from what i hear and how i understand the&#xA;Tufin platform&lt;/li&gt;&#xA;&lt;li&gt;Zoning or very wide segmentation is nice, but what you really want is to be&#xA;able to do finer grained segmentation without modifying or rearchitecting the&#xA;network&lt;/li&gt;&#xA;&lt;li&gt;relying on hardware firewalls will never be able to free you from the&#xA;constraints of those devices, especially throughput limits, the hardware&#xA;cycle that will just happen every three or five years and the inability of a&#xA;firewall to really be point to point and not zone to zone&lt;/li&gt;&#xA;&lt;li&gt;i would assume that the integration of this is very hard, thanks god it is&#xA;usually owned by just one team, but what about outsourcers and system integrators?&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Sage Data Security on why network segmentation is important</title>
      <link>https://microsegment.io/post/2019-10-14-sage-on-network-segmentation/</link>
      <pubDate>Mon, 14 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-10-14-sage-on-network-segmentation/</guid>
      <description>&lt;p&gt;Nice &lt;a href=&#34;https://www.sagedatasecurity.com/blog/the-security-benefits-of-network-segmentation?utm_campaign=Blog&amp;amp;amp;utm_content=102297858&amp;amp;amp;utm_medium=social&amp;amp;amp;utm_source=twitter&amp;amp;amp;hss_channel=tw-2317931713&#34;&gt;article from Sage Data Security&lt;/a&gt; on&#xA;why network segmentation is important.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying Cisco ACI and VMware NSX</title>
      <link>https://microsegment.io/post/2019-10-12-deploying-cisco-aci-and-vmware-nsx/</link>
      <pubDate>Sat, 12 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-10-12-deploying-cisco-aci-and-vmware-nsx/</guid>
      <description>&lt;p&gt;One of my favourite networking podcasts,&#xA;&lt;a href=&#34;https://packetpushers.net/&#34;&gt;PacketPushers&lt;/a&gt; has a &lt;a href=&#34;podcast/heavy-networking-476-running-aci-and-nsx-in-the-same-data-center/&#34;&gt;great episode on integrating&#xA;Cisco ACI and VMware NSX at the same&#xA;time&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;I really enjoyed listening to this episode, one reason for sure was that&#xA;Derek Wilson seems to be a really nice and knowledgeable person, but the other&#xA;is that he shared some valuable insights into deploying ACI and its uses for&#xA;big companies.&lt;/p&gt;&#xA;&lt;p&gt;My key takeaways from the episode are:&lt;/p&gt;</description>
    </item>
    <item>
      <title>NIST publishes a zerotrust architecture recommendation</title>
      <link>https://microsegment.io/post/2019-10-11-nist-publishes-zerotrust-architecture-recommendation/</link>
      <pubDate>Fri, 11 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-10-11-nist-publishes-zerotrust-architecture-recommendation/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://nist.gov/&#34;&gt;US NIST&lt;/a&gt; published a great guide on a zero trust&#xA;architecture that definitely is worth reading and details the elements,&#xA;deployment and deployment scenarios and reference to other material to help&#xA;people get started with zero trust.&lt;/p&gt;&#xA;&lt;p&gt;&lt;span class=&#34;inline-svg-icon&#34; &gt;&lt;svg xmlns=&#34;http://www.w3.org/2000/svg&#34; viewBox=&#34;0 0 384 512&#34;&gt;&lt;path fill=&#34;currentColor&#34; d=&#34;M181.9 256.1c-5-16-4.9-46.9-2-46.9 8.4 0 7.6 36.9 2 46.9zm-1.7 47.2c-7.7 20.2-17.3 43.3-28.4 62.7 18.3-7 39-17.2 62.9-21.9-12.7-9.6-24.9-23.4-34.5-40.8zM86.1 428.1c0 .8 13.2-5.4 34.9-40.2-6.7 6.3-29.1 24.5-34.9 40.2zM248 160h136v328c0 13.3-10.7 24-24 24H24c-13.3 0-24-10.7-24-24V24C0 10.7 10.7 0 24 0h200v136c0 13.2 10.8 24 24 24zm-8 171.8c-20-12.2-33.3-29-42.7-53.8 4.5-18.5 11.6-46.6 6.2-64.2-4.7-29.4-42.4-26.5-47.8-6.8-5 18.3-.4 44.1 8.1 77-11.6 27.6-28.7 64.6-40.8 85.8-.1 0-.1.1-.2.1-27.1 13.9-73.6 44.5-54.5 68 5.6 6.9 16 10 21.5 10 17.9 0 35.7-18 61.1-61.8 25.8-8.5 54.1-19.1 79-23.2 21.7 11.8 47.1 19.5 64 19.5 29.2 0 31.2-32 19.7-43.4-13.9-13.6-54.3-9.7-73.6-7.2zM377 105L279 7c-4.5-4.5-10.6-7-17-7h-6v128h128v-6.1c0-6.3-2.5-12.4-7-16.9zm-74.1 255.3c4.1-2.7-2.5-11.9-42.8-9 37.1 15.8 42.8 9 42.8 9z&#34;/&gt;&lt;/svg&gt;&#xA;&lt;/span&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ideas on Segmentation metrics (part three)</title>
      <link>https://microsegment.io/2019/10/02/metrics-for-security-segmentation-part-three/</link>
      <pubDate>Wed, 02 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/10/02/metrics-for-security-segmentation-part-three/</guid>
      <description>&lt;p&gt;&lt;span class=&#34;inline-svg-icon&#34; &gt;&lt;svg xmlns=&#34;http://www.w3.org/2000/svg&#34; viewBox=&#34;0 0 576 512&#34;&gt;&lt;path fill=&#34;currentColor&#34; d=&#34;M542.22 32.05c-54.8 3.11-163.72 14.43-230.96 55.59-4.64 2.84-7.27 7.89-7.27 13.17v363.87c0 11.55 12.63 18.85 23.28 13.49 69.18-34.82 169.23-44.32 218.7-46.92 16.89-.89 30.02-14.43 30.02-30.66V62.75c.01-17.71-15.35-31.74-33.77-30.7zM264.73 87.64C197.5 46.48 88.58 35.17 33.78 32.05 15.36 31.01 0 45.04 0 62.75V400.6c0 16.24 13.13 29.78 30.02 30.66 49.49 2.6 149.59 12.11 218.77 46.95 10.62 5.35 23.21-1.94 23.21-13.46V100.63c0-5.29-2.62-10.14-7.27-12.99z&#34;/&gt;&lt;/svg&gt;&#xA;&lt;/span&gt;&#xA;Please check out &lt;a href=&#34;https://microsegment.io/2019/08/22/metrics-for-security-segmentation-part-one/&#34;&gt;Part&#xA;one&lt;/a&gt; and &lt;a href=&#34;https://microsegment.io/2019/09/02/metrics-for-security-segmentation-part-two/&#34;&gt;part two of&#xA;this series&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Continuing our series about metrics for segmentation, there are a couple more&#xA;angles how you can measure the effectiveness of your segmentation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>8 Microsegmentation pitfalls to avoid</title>
      <link>https://microsegment.io/post/2019-09-30-eight-microsegmentation-pitfalls-to-avoid/</link>
      <pubDate>Mon, 30 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-09-30-eight-microsegmentation-pitfalls-to-avoid/</guid>
      <description>&lt;p&gt;I read a nice article by &lt;a href=&#34;https://www.darkreading.com/author-bio.asp?author_id=962&#34;&gt;Ericka&#xA;Chickowski&lt;/a&gt; on&#xA;&lt;a href=&#34;https://www.darkreading.com/8-microsegmentation-pitfalls-to-avoid/d/d-id/1335936?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple&#34;&gt;Darkreading&lt;/a&gt;&#xA;the other day. The article gives some great guidance on what to do and not to&#xA;do when starting your segmentation journey. Here are some comments.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;The practice of microsegmentation takes the principles of least privilege to&#xA;their logical conclusion by atomizing the isolating techniques of network&#xA;segmentation. Security architects use microsegmentation to create security&#xA;boundaries that can extend all the way into individual workloads by&#xA;controlling East-West, or server-to-server, traffic flows between&#xA;applications. The bulkheads put up through microsegmentation make it possible&#xA;to better limit lateral movement of attackers, even in a cloudy world with no&#xA;perimeter.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The incomplete ITSA 2019 guide to segmentation</title>
      <link>https://microsegment.io/post/2019-10-01-the-incomplete-itsa-guide-to-segmentation/</link>
      <pubDate>Mon, 30 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-10-01-the-incomplete-itsa-guide-to-segmentation/</guid>
      <description>&lt;p&gt;Next week it is the &lt;a href=&#34;https://www.it-sa.de/&#34;&gt;ITSA 2019&lt;/a&gt; in Nuremberg and i thought&#xA;it will be good to give you high priests of segmentation a overview of the&#xA;companies exhibiting their solutions for &lt;strong&gt;segmentation&lt;/strong&gt; and&#xA;&lt;strong&gt;microsegmentation&lt;/strong&gt; there.&lt;/p&gt;&#xA;&lt;h2 id=&#34;illumio&#34;&gt;Illumio&lt;/h2&gt;&#xA;&lt;p&gt;This one is special, because you will have the chance to meet me personally&#xA;presenting the power of host-based microsegmentation to you for the three days&#xA;of ITSA 2019. Feel free to come by and ask me anything about Illumio, this site&#xA;or really anything that comes up.&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>
    <item>
      <title>Undivided We Fall: Decoupling Network Segmentation from Micro-Segmentation</title>
      <link>https://microsegment.io/post/2019-09-12-decoupling-network-segmentation-from-microsegmentation/</link>
      <pubDate>Thu, 12 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-09-12-decoupling-network-segmentation-from-microsegmentation/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://twitter.com/alissaknight&#34;&gt;@alissaknight &lt;/a&gt; has published a&#xA;&lt;a href=&#34;https://www.linkedin.com/pulse/undivided-we-fall-decoupling-network-segmentation-valentina-knight/&#34;&gt;great article&lt;/a&gt;&#xA;on LinkedIn that talks about the history of segmentation and the use-cases&#xA;and differences of network segmentation and micro-segmentation.&lt;/p&gt;&#xA;&lt;p&gt;What i like about the article is that Alissa shows that network segmentation&#xA;and micro-segmentation can be mutually exclusive, but can also co-exist. They&#xA;do different things and they have different use-cases, which are also highlighted&#xA;in the article.&lt;/p&gt;&#xA;&lt;p&gt;The conclusion though is what i wouldn&amp;rsquo;t agree to, a Software Defined Perimeter&#xA;does not solve a lateral movement problem nor will it implement Micro-Segmentation.&#xA;The underlying problem of having no visibility into what to segment and how&#xA;to structure your policy so it does not break applications is not solved by&#xA;moving to another solution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Demystifying the Windows Firewall</title>
      <link>https://microsegment.io/post/2019-09-10-link-demystifying-the-windows-firewall/</link>
      <pubDate>Tue, 10 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-09-10-link-demystifying-the-windows-firewall/</guid>
      <description>&lt;p&gt;What a great talk by &lt;a href=&#34;https://twitter.com/jepaynemsft&#34;&gt;Jessica Payne&lt;/a&gt; that talks&#xA;about why network segmentation is so important and how to apply these principles&#xA;to your host-based Windows Firewall (that you probably never use).&#xA;It is from 2016 and still true.&lt;/p&gt;&#xA;&lt;iframe&#xA;src=&#34;https://channel9.msdn.com/Events/Ignite/New-Zealand-2016/M377/player&#34;&#xA;width=&#34;960&#34; height=&#34;540&#34; allowFullScreen frameBorder=&#34;0&#34; title=&#34;Demystifying&#xA;the Windows Firewall – Learn how to irritate attackers without crippling your&#xA;network - Microsoft Channel 9 Video&#34;&gt;&lt;/iframe&gt;</description>
    </item>
    <item>
      <title>Scaling up vs scaling out your security segmentation</title>
      <link>https://microsegment.io/post/2019-09-15-scale-up-vs-scale-out/</link>
      <pubDate>Mon, 09 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-09-15-scale-up-vs-scale-out/</guid>
      <description>&lt;p&gt;&#xA;  &lt;img src=&#34;https://microsegment.io/img/scale-up-vs-scale-out.png&#34; alt=&#34;Scale-up-vs-scale-out&#34;&gt;&#xA;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;If you follow discussion on running cloud native, monolithic or more&#xA;traditional applications you may have stumbled over the terms &amp;ldquo;scale up“ and&#xA;&amp;ldquo;scale out“. Don’t feel bad if you don’t know these, because they were formerly&#xA;just &amp;ldquo;vertical scaling“ (scale up) and &amp;ldquo;horizontal scaling“ (scale out).&lt;/p&gt;&#xA;&lt;h1 id=&#34;what-is-scale-up&#34;&gt;What is scale up?&lt;/h1&gt;&#xA;&lt;p&gt;Scale up means, if you have e.g. a server in your datacenter running your&#xA;database, to make the database faster or have more concurrent client getting&#xA;served, you would add more hardware to that server and just make it the biggest&#xA;machine available.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Segment-O-Pedia</title>
      <link>https://microsegment.io/post/segment-o-pedia/</link>
      <pubDate>Fri, 06 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/segment-o-pedia/</guid>
      <description>&lt;p&gt;&lt;span class=&#34;inline-svg-icon&#34; &gt;&lt;svg xmlns=&#34;http://www.w3.org/2000/svg&#34; viewBox=&#34;0 0 512 512&#34;&gt;&lt;path fill=&#34;currentColor&#34; d=&#34;M501.1 395.7L384 278.6c-23.1-23.1-57.6-27.6-85.4-13.9L192 158.1V96L64 0 0 64l96 128h62.1l106.6 106.6c-13.6 27.8-9.2 62.3 13.9 85.4l117.1 117.1c14.6 14.6 38.2 14.6 52.7 0l52.7-52.7c14.5-14.6 14.5-38.2 0-52.7zM331.7 225c28.3 0 54.9 11 74.9 31l19.4 19.4c15.8-6.9 30.8-16.5 43.8-29.5 37.1-37.1 49.7-89.3 37.9-136.7-2.2-9-13.5-12.1-20.1-5.5l-74.4 74.4-67.9-11.3L334 98.9l74.4-74.4c6.6-6.6 3.4-17.9-5.7-20.2-47.4-11.7-99.6.9-136.6 37.9-28.5 28.5-41.9 66.1-41.2 103.6l82.1 82.1c8.1-1.9 16.5-2.9 24.7-2.9zm-103.9 82l-56.7-56.7L18.7 402.8c-25 25-25 65.5 0 90.5s65.5 25 90.5 0l123.6-123.6c-7.6-19.9-9.9-41.6-5-62.7zM64 472c-13.2 0-24-10.8-24-24 0-13.3 10.7-24 24-24s24 10.7 24 24c0 13.2-10.7 24-24 24z&#34;/&gt;&lt;/svg&gt;&#xA;&lt;/span&gt;&#xA;This page is work in progress. If there is something&#xA;missing feel free to comment or send me a mail.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ideas on Segmentation metrics (part two)</title>
      <link>https://microsegment.io/2019/09/02/metrics-for-security-segmentation-part-two/</link>
      <pubDate>Mon, 02 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/09/02/metrics-for-security-segmentation-part-two/</guid>
      <description>&lt;p&gt;&lt;span class=&#34;inline-svg-icon&#34; &gt;&lt;svg xmlns=&#34;http://www.w3.org/2000/svg&#34; viewBox=&#34;0 0 576 512&#34;&gt;&lt;path fill=&#34;currentColor&#34; d=&#34;M542.22 32.05c-54.8 3.11-163.72 14.43-230.96 55.59-4.64 2.84-7.27 7.89-7.27 13.17v363.87c0 11.55 12.63 18.85 23.28 13.49 69.18-34.82 169.23-44.32 218.7-46.92 16.89-.89 30.02-14.43 30.02-30.66V62.75c.01-17.71-15.35-31.74-33.77-30.7zM264.73 87.64C197.5 46.48 88.58 35.17 33.78 32.05 15.36 31.01 0 45.04 0 62.75V400.6c0 16.24 13.13 29.78 30.02 30.66 49.49 2.6 149.59 12.11 218.77 46.95 10.62 5.35 23.21-1.94 23.21-13.46V100.63c0-5.29-2.62-10.14-7.27-12.99z&#34;/&gt;&lt;/svg&gt;&#xA;&lt;/span&gt;&#xA;Please check out &lt;a href=&#34;https://microsegment.io/2019/08/22/metrics-for-security-segmentation-part-one/&#34;&gt;Part one of this series of&#xA;articles&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h1 id=&#34;metric-one-do-you-have-more-than-one-segment&#34;&gt;Metric One: Do you have more than one segment?&lt;/h1&gt;&#xA;&lt;p&gt;&lt;span class=&#34;inline-svg-icon&#34; &gt;&lt;svg xmlns=&#34;http://www.w3.org/2000/svg&#34; viewBox=&#34;0 0 640 512&#34;&gt;&lt;path fill=&#34;currentColor&#34; d=&#34;M640 264v-16c0-8.84-7.16-16-16-16H344v-40h72c17.67 0 32-14.33 32-32V32c0-17.67-14.33-32-32-32H224c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h72v40H16c-8.84 0-16 7.16-16 16v16c0 8.84 7.16 16 16 16h104v40H64c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h160c17.67 0 32-14.33 32-32V352c0-17.67-14.33-32-32-32h-56v-40h304v40h-56c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h160c17.67 0 32-14.33 32-32V352c0-17.67-14.33-32-32-32h-56v-40h104c8.84 0 16-7.16 16-16zM256 128V64h128v64H256zm-64 320H96v-64h96v64zm352 0h-96v-64h96v64z&#34;/&gt;&lt;/svg&gt;&#xA;&lt;/span&gt;&#xA;This question is, of course, more of a&#xA;rhetorical question, but there is a point about this one. Of course almost all&#xA;companies have more than one segment. Most companies use VLANs extensively. We&#xA;break out DMZs and internal data center LANs of course.  Sometimes we use&#xA;firewall interfaces between those VLANs or segments and treat them as zones.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ACT IAC on Zero Trust trends</title>
      <link>https://microsegment.io/post/2019-08-25-actiac-zero-trust-cybersecurity-trends/</link>
      <pubDate>Sun, 25 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2019-08-25-actiac-zero-trust-cybersecurity-trends/</guid>
      <description>&lt;p&gt;The &lt;strong&gt;American Council for Technology-Industry Advisory Council (ACT-IAC)&lt;/strong&gt;, a&#xA;non commercial organisation for creating a more innovative government published&#xA;a &lt;a href=&#34;https://www.actiac.org/system/files/ACT-IAC%20Zero%20Trust%20Project%20Report%2004182019.pdf&#34;&gt;paper on Zero&#xA;Trust&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;I would recommend this paper for anybody remotely thinking about Zero Trust,&#xA;be it because you start thinking about introducing it or because it is just&#xA;one of those trends that you want to catch up on.&lt;/p&gt;&#xA;&lt;p&gt;There is a huge amount of truth and knowledge in this document and it is&#xA;not having any marketing in it. I read it and thought this is sound advice&#xA;for anyone that looks to improve their security posture with the ultimate,&#xA;long term &lt;strong&gt;Zero Trust&lt;/strong&gt; goal in mind.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ideas on segmentation metrics (part one)</title>
      <link>https://microsegment.io/2019/08/22/metrics-for-security-segmentation-part-one/</link>
      <pubDate>Thu, 22 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/08/22/metrics-for-security-segmentation-part-one/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;What you measure is what you get&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;If you are like me and live and breath IT or IT security, the above statement&#xA;probably does not ring a bell and you don&amp;rsquo;t realize the source of this.&#xA;It is from a person called &lt;a href=&#34;https://en.wikipedia.org/wiki/Robert_S._Kaplan&#34;&gt;Robert. S. Kaplan&lt;/a&gt;&#xA;who developed something you may have heard of, the balanced scorecard.&lt;/p&gt;&#xA;&lt;p&gt;I will not dig into economics, because we are not in business school,&#xA;but the essence of the scorecard is that you need metrics on which you&#xA;can measure success or failure to be successful or be able to reach&#xA;your objectives.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A short history of segmentation</title>
      <link>https://microsegment.io/2019/08/19/a-short-history-of-segmentation/</link>
      <pubDate>Mon, 19 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/08/19/a-short-history-of-segmentation/</guid>
      <description>&lt;p&gt;&#xA;  &lt;img src=&#34;https://microsegment.io/img/ethernet-timeline.png&#34; alt=&#34;The ethernet timeline&#34;&gt;&#xA;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s start this with quoting wikipedia on what &lt;em&gt;network segmentation&lt;/em&gt; is according&#xA;to a encyclopedia.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Network segmentation in computer networking is the act or practice of&#xA;splitting a computer network into subnetworks, each being a network segment.&#xA;Advantages of such splitting are primarily for boosting performance and&#xA;improving security.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;h1 id=&#34;how-did-this-start&#34;&gt;How did this start?&lt;/h1&gt;&#xA;&lt;p&gt;&#xA;  &lt;img src=&#34;https://microsegment.io/img/ethernet-history.jpg&#34; alt=&#34;First ethernet draft&#34;&gt;&#xA;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;Some of the readers might actually be old enough to remember how &lt;em&gt;local area&#xA;networks&lt;/em&gt; started out in the early 90s.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A collection of zero trust resources</title>
      <link>https://microsegment.io/post/zero-trust-resources/</link>
      <pubDate>Sat, 10 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/zero-trust-resources/</guid>
      <description>&lt;h1 id=&#34;work-in-progress&#34;&gt;Work in progress&lt;/h1&gt;&#xA;&lt;p&gt;This list is work in progress, if you have suggestions on what to add,&#xA;please add a comment below or drop me a mail or note.&lt;/p&gt;&#xA;&lt;h1 id=&#34;the-origins&#34;&gt;The origins&lt;/h1&gt;&#xA;&lt;p&gt;Zero Trust is not exactly a new idea, but a name for a architecture that takes&#xA;least privilege as the first design principle and assumes nothing can be&#xA;trusted.  I am not sure who established the category at this moment, but it&#xA;seems Google and Forrester Research have both been working on this.  &lt;a href=&#34;https://twitter.com/kindervag&#34;&gt;John&#xA;Kindervag (@kindervag)&lt;/a&gt; originally published the&#xA;model in 2010.&#xA;That paper is still valid 9 years after the first publication and it shows&#xA;great foresight and vision. Kudos to that.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Visualization of an attack in a Zero Trust Network</title>
      <link>https://microsegment.io/2019/08/10/visualization-of-an-attack-zero-trust/</link>
      <pubDate>Sat, 10 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/08/10/visualization-of-an-attack-zero-trust/</guid>
      <description>&lt;p&gt;Dr Chase Cunningham from Forrester Research is spreading the Zero Trust&#xA;Networking word and there is a lot to be learned from the model.&#xA;The below video shows how a attack spreads in a relatively flat network&#xA;compared to how it spreads (or rather does not spread) in a network&#xA;build with Zero Trust Networking architecture.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://go.forrester.com/blogs/zero-trust-in-practice/&#34;&gt;Zero Trust in Practice&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;We will also publish a series of posts and articles that talk about&#xA;the Zero Trust model, the guiding principles and challenges and how&#xA;to start the journey.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microservices and microsegmentation</title>
      <link>https://microsegment.io/2019/08/07/microservices-and-microsegmentation/</link>
      <pubDate>Wed, 07 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/08/07/microservices-and-microsegmentation/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://dzone.com/articles/microservices-versus-microsegmentation&#34;&gt;Microsegmentation and microservices&lt;/a&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;found this article on DZone and wanted to quickly share my thoughts on it.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&amp;ldquo;Micro is big these days&amp;rdquo; - This statement is from a 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;&#xA;&lt;p&gt;Microservices are about dissecting applications to smaller units and run those&#xA;units independently instead of running them in a monolithic application. This&#xA;creates the ability to decouple those functions and makes the service more&#xA;scalable, independent from the other services and easier to maintain a single&#xA;functionality. Often one team is responsible for one microservice. They maintain&#xA;their interface, but consumers of the service do not have to worry about the&#xA;inner workings as long as they stick to the public interface.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kubernetes podcast on attacking k8s</title>
      <link>https://microsegment.io/2019/08/06/attacking-kubernetes/</link>
      <pubDate>Tue, 06 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/2019/08/06/attacking-kubernetes/</guid>
      <description>&lt;p&gt;The current &lt;a href=&#34;https://kubernetespodcast.com/episode/065-attacking-and-defending-kubernetes/&#34;&gt;Kubernetes Podcast&lt;/a&gt;&#xA;gives a great view into how to attack kubernetes clusters. I have been talking&#xA;about this all the time when i see OpenShift or kubernetes clusters that are trying&#xA;to protect the container infrastructure with tools made for protecting pods, but&#xA;hardly protect the container orchestration platform itself.&lt;/p&gt;&#xA;&lt;p&gt;Securing the container infrastructure is hard and not doing it may lead to&#xA;things like cluster takeover or host escapes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>microsegment.io started</title>
      <link>https://microsegment.io/2019/08/04/microsegment-io-started/</link>
      <pubDate>Sun, 04 Aug 2019 11:24:02 +0200</pubDate>
      <guid>https://microsegment.io/2019/08/04/microsegment-io-started/</guid>
      <description>&lt;h1 id=&#34;welcome-to-microsegmentio&#34;&gt;Welcome to microsegment.io&lt;/h1&gt;&#xA;&lt;p&gt;microsegment.io is a site to post news and discuss new developments, products,&#xA;common problems and best practices all around microsegmentation and a broader&#xA;discussion around segmenting your network to make it more secure and resilient&#xA;to attacks.&#xA;We may also highlight current topics like automation, integration and the segmentation&#xA;of (not so) new technology like containers and service meshes.&#xA;The information you will find will be technical, but mostly not down to a binary level.&lt;/p&gt;</description>
    </item>
    <item>
      <title>An Example Post</title>
      <link>https://microsegment.io/post/2020-03-27-dealing-with-remote-work/</link>
      <pubDate>Mon, 04 Jun 2018 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2020-03-27-dealing-with-remote-work/</guid>
      <description></description>
    </item>
  </channel>
</rss>
