<?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: Config - Arista Macro Segmentation Service (MSS) + Check Point in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/135535#M20443</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/38448"&gt;@bogdanp&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;Unfortunately there are no official document from Check Point here.&lt;/P&gt;
&lt;P&gt;I would contact a local Check Point SE.&lt;/P&gt;</description>
    <pubDate>Sun, 05 Dec 2021 13:47:29 GMT</pubDate>
    <dc:creator>HeikoAnkenbrand</dc:creator>
    <dc:date>2021-12-05T13:47:29Z</dc:date>
    <item>
      <title>Config - Arista Macro Segmentation Service (MSS) + Check Point</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/118779#M16820</link>
      <description>&lt;P&gt;Modern day applications deployed in the data centers have become multi-tiered and distributed. This has resulted in an increase&lt;BR /&gt;in the amount of east-west traffic seen in the data centers. This includes traffic from physical-to-physical (P-to-P), virtual-to-virtual (V-to-V), and between physical and virtual (P-to-V) workload.&lt;/P&gt;
&lt;P&gt;Arista Macro-Segmentation Service (MSS) provides a software-driven dynamic and scalable network service to logically insert&lt;BR /&gt;security devices into the path of traffic with complete flexibility on placement of security devices and workloads. It is specifically&lt;BR /&gt;aimed at physical-to-physical (P-to-P) and physical-to-virtual (P-to-V) workloads.&lt;BR /&gt;What makes MSS unique is that it places the control of policy enforcement directly in the hands of security administrators. This is&lt;BR /&gt;accomplished using standards based forwarding with no proprietary frame formats and without placing limitations on where the&lt;BR /&gt;service devices must exist within the network.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Arista MSS Deployment Mode:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;Many data centers have firewalls deployed in layer-3 mode, acting as first hop for the hosts, serving applications. The Layer 3 Firewall&lt;BR /&gt;is connected to the network and configured to enforce policy between different security zones or endpoints.&lt;BR /&gt;Instead of using routing policy to attract traffic to the firewall, the Macro-Segmentation Service redirects traffic to the firewall,&lt;BR /&gt;dynamically inserting it into the path for traffic between relevant endpoints. L3 Firewall is not configured as a gateway for the&lt;BR /&gt;subnet.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Requirements: &lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;• Arista CloudVision running EOS release 4.23.2F or later&lt;BR /&gt;• Management Server Versions&lt;BR /&gt;• Version R80.30 with API version 1.5 (and above). In addition to this Management Server version, Check Point has provided&lt;BR /&gt;a “hot fix” that provides a “Proxy API” ability which allows the user to access the Gateway APIs through a special URL on the&lt;BR /&gt;Management Server. This hot-fix is required for MSS to work.&lt;BR /&gt;• Gateway Versions: Version R80.30 with API version 1.2 (and above)&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;Config example:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Direct Flow is enabled on all TOR switches with 100Gbps Interfaces:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;!
cvx
no shutdown
!
service mss
no shutdown
policy enforcement rules verbatim
!
dynamic device-set checkpoint
device 10.0.0.200
username admin password 7 xxxxxxxxxxxxxxxx
protocol https 4434
group poc-mss
state active
type check-point management-server
policy tag redirect MSS_redirect
policy tag offload MSS_offload
policy tag modifier verbatim MSS_verbatim
!
service vxlan
no shutdown&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Check Point:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Interface Configurations:&lt;BR /&gt;&lt;BR /&gt;Interfaces configured in aggregation groups bond1.100 and bond1.200. bond1.100 is part of the zone ‘Tenant C’ and bond1.200 is&lt;BR /&gt;part of the zone ‘Tenant D’&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Arista_1.PNG" style="width: 646px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/11730i3A9AF771946E2A2E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Arista_1.PNG" alt="Arista_1.PNG" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Route Configuration:&lt;/STRONG&gt; &lt;BR /&gt;&lt;BR /&gt;The firewall needs to have routes back to the original subnets in which the end hosts reside. Static routes have been created for each subnet. Default GW for the Tenant C subnets is the VLAN 10 interface on the TOR and for Tenant D subnets its the VLAN 20 interface on the TOR.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Arista_2.PNG" style="width: 655px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/11731i36128F32708AE045/image-size/large?v=v2&amp;amp;px=999" role="button" title="Arista_2.PNG" alt="Arista_2.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Policy Configuration:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;For Tenant C:&lt;BR /&gt;• Web servers can talk to each other directly only on port 443 or port 80 the web servers are connected directly on the same VLAN and IP subnet.&lt;BR /&gt;• Web Servers can communicate with the proxy servers on port 8080 HTTP as well.&lt;BR /&gt;For Tenant D :&lt;BR /&gt;• Web servers can talk to each other directly only on port 443 or port 80 the web servers are connected directly on the same VLAN and IP subnet.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Arista_5.PNG" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/11733i6DCB5C753EC2A509/image-size/large?v=v2&amp;amp;px=999" role="button" title="Arista_5.PNG" alt="Arista_5.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;For Tenant C, firewall policy tags defined as “MSS-redirect” (red)&amp;nbsp; are enforced by the Active Firewall.&lt;BR /&gt;&lt;BR /&gt;For Tenant C for proxy, Firewall tags defined as “MSS-offload” (blue) are enforced by the Arista switches locally without being redirected to the Active firewall.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 May 2021 17:23:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/118779#M16820</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2021-05-20T17:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: Config - Arista Macro Segmentation Service (MSS) + Check Point</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/118781#M16822</link>
      <description>&lt;P&gt;Is there detailed documentation from Check Point side for this Arista MSS feature with configuration examples?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 May 2021 09:22:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/118781#M16822</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2021-05-19T09:22:50Z</dc:date>
    </item>
    <item>
      <title>Re: Config - Arista Macro Segmentation Service (MSS) + Check Point</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/135504#M20421</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I am also interested in this solution. The only documents I have found so far regarding this solution were on the Arista websites (Arista EOS Central).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If someone has more input on this topic, I think it is trully welcomed.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Dec 2021 11:02:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/135504#M20421</guid>
      <dc:creator>bogdanp</dc:creator>
      <dc:date>2021-12-04T11:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: Config - Arista Macro Segmentation Service (MSS) + Check Point</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/135535#M20443</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/38448"&gt;@bogdanp&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;Unfortunately there are no official document from Check Point here.&lt;/P&gt;
&lt;P&gt;I would contact a local Check Point SE.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Dec 2021 13:47:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Config-Arista-Macro-Segmentation-Service-MSS-Check-Point/m-p/135535#M20443</guid>
      <dc:creator>HeikoAnkenbrand</dc:creator>
      <dc:date>2021-12-05T13:47:29Z</dc:date>
    </item>
  </channel>
</rss>

