<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Microsegmentation with Firewall Hardware in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253472#M42547</link>
    <description>&lt;P&gt;It depends on the hypervisor's capabilities. It needs to support private VLANs, MPLS-based flow control, or an analogous feature. I haven't followed ESX development in years, but it looks like they have at least some support for private VLANs.&lt;/P&gt;</description>
    <pubDate>Fri, 18 Jul 2025 17:22:32 GMT</pubDate>
    <dc:creator>Bob_Zimmerman</dc:creator>
    <dc:date>2025-07-18T17:22:32Z</dc:date>
    <item>
      <title>Microsegmentation with Firewall Hardware</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253382#M42520</link>
      <description>&lt;P&gt;Hello Community ,&lt;/P&gt;&lt;P&gt;I need your help and suggestions .&lt;/P&gt;&lt;P&gt;Our client is adopting an SDN architecture, and we've proposed Checkpoint as a firewall that will perform microsegmentation in the fabric .&lt;BR /&gt;Let's assume a physical server hosting VMs at the hypervisor level connected to a leaf switch. How will we technically inspect inter-VM traffic, given that the proposed firewall is hardware-based? How can we achieve the same functionality as CloudGuard?&lt;BR /&gt;For information, the firewall is located in a service bridge domain, allowing it to operate within graph contract services. But we don't know how tu push the traffic outside , inspect and then back to the hypervisor to the VM at the destination .&lt;/P&gt;&lt;P&gt;Thanks for your help&amp;nbsp;&lt;/P&gt;&lt;P&gt;Imad&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jul 2025 15:03:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253382#M42520</guid>
      <dc:creator>Imad981</dc:creator>
      <dc:date>2025-07-17T15:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: Microsegmentation with Firewall Hardware</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253388#M42521</link>
      <description>&lt;P&gt;First, microsegmentation is a &lt;EM&gt;&lt;STRONG&gt;grave mistake&lt;/STRONG&gt;&lt;/EM&gt;. It's a maintenance nightmare and actively encourages people to build applications in ways which are extraordinarily difficult to reason confidently about when troubleshooting. I say this from extensive, painful experience.&lt;/P&gt;
&lt;P&gt;If you are &lt;STRONG&gt;absolutely sure&lt;/STRONG&gt; you want to wreck the datacenter, it's possible to do as long as your switches and your hypervisor platform support private VLANs. It could also be done with MPLS route distinguishers (I originally misspoke and said "descriptors") and route targets, but that's much more exotic, so you're less likely to find people who can support MPLS in this way. Give all of your VMs and physical endpoints (not the firewalls) a 32-bit (or 128-bit for IPv6) netmask and a gateway address. Give your firewalls the normal netmask. When endpoints try to go anywhere, the frame goes to the gateway's MAC. The gateway then filters it and sends it back out the same interface to the destination. The private VLANs or MPLS configuration enforce this traffic pattern, so a misconfigured VM or physical host can't talk to anything on its local network.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jul 2025 17:15:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253388#M42521</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2025-07-18T17:15:57Z</dc:date>
    </item>
    <item>
      <title>Re: Microsegmentation with Firewall Hardware</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253393#M42523</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/27871"&gt;@Bob_Zimmerman&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your answer , but in this way can we enforce the traffic&amp;nbsp;is routed out of the hypervisor (host ESXi for example) and into the hardware firewall?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jul 2025 16:44:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253393#M42523</guid>
      <dc:creator>Imad981</dc:creator>
      <dc:date>2025-07-17T16:44:40Z</dc:date>
    </item>
    <item>
      <title>Re: Microsegmentation with Firewall Hardware</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253472#M42547</link>
      <description>&lt;P&gt;It depends on the hypervisor's capabilities. It needs to support private VLANs, MPLS-based flow control, or an analogous feature. I haven't followed ESX development in years, but it looks like they have at least some support for private VLANs.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jul 2025 17:22:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Microsegmentation-with-Firewall-Hardware/m-p/253472#M42547</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2025-07-18T17:22:32Z</dc:date>
    </item>
  </channel>
</rss>

