<?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: Split tunnel - URL resolution &amp;quot;IPaddressFeed2CheckPoint&amp;quot; script for windows updates in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunnel-URL-resolution-quot-IPaddressFeed2CheckPoint-quot/m-p/120794#M8460</link>
    <description>&lt;P&gt;First of all, I think the requirement to "route all traffic" is...untenable for a variety of reasons.&lt;BR /&gt;A better approach would be to have the appropriate controls on the Endpoint (Harmony Endpoint/Browse) so routing the traffic back to a headend isn't necessary.&lt;/P&gt;
&lt;P&gt;Having said that, I imagine this code could (with modifications, likely) also work for the purpose of creating an encryption domain.&lt;BR /&gt;The main thing is that the output must be IP addresses, since you have to create regular network/host objects.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Jun 2021 23:16:51 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2021-06-09T23:16:51Z</dc:date>
    <item>
      <title>Split tunnel - URL resolution "IPaddressFeed2CheckPoint" script for windows updates</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunnel-URL-resolution-quot-IPaddressFeed2CheckPoint-quot/m-p/120732#M8459</link>
      <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Requirement ::&amp;nbsp;&lt;/P&gt;&lt;P&gt;Split tunneling for windows updates.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Background ::&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customer using exclusion group for Split Tunneling with address ranges as per&amp;nbsp;sk167000 for o365, windows updates are new requirement. There does not appear to be a Microsoft official &lt;STRONG&gt;&lt;EM&gt;feed&lt;/EM&gt;&lt;/STRONG&gt; for domains/address ranges as with o365 &amp;amp; updatable/FQDN objects are unsupported for encryption domain related configuration as per &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;'s&amp;nbsp;comment in thread &lt;A href="https://community.checkpoint.com/t5/Remote-Access-VPN/Split-tunnel-to-Microsoft-Office-365-YouTube-or-other-services/td-p/80040" target="_blank" rel="noopener"&gt;https://community.checkpoint.com/t5/Remote-Access-VPN/Split-tunnel-to-Microsoft-Office-365-YouTube-or-other-services/td-p/80040&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In sk167000 point #11 outlines "&lt;SPAN&gt;Automate Office 365 address updates by importing IP Address objects directly from Microsoft’s public feed using the&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://github.com/CheckPointSW-Community/IPaddressFeed2CheckPoint" target="_blank" rel="noopener"&gt;IPaddressFeed2CheckPoint&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;script from our Community Github page."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From script using feed ::&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN class="pl-c"&gt;#Download of Feed&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;curl_cli --insecure &lt;SPAN class="pl-s"&gt;&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;&lt;A href="https://endpoints.office.com/endpoints/worldwide?noipv6&amp;amp;ClientRequestId=b10c5ed1-bad1-445f-b386-b919946339a7" target="_blank" rel="noopener"&gt;https://endpoints.office.com/endpoints/worldwide?noipv6&amp;amp;ClientRequestId=b10c5ed1-bad1-445f-b386-b919946339a7&lt;/A&gt;&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class="pl-k"&gt;|&lt;/SPAN&gt; jq &lt;SPAN class="pl-s"&gt;&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;.[] | select(.category=="Optimize")&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class="pl-k"&gt;|&lt;/SPAN&gt; grep -o &lt;SPAN class="pl-s"&gt;&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}\/[0-9]\{1,\}&lt;SPAN class="pl-pds"&gt;'&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class="pl-k"&gt;&amp;gt;&lt;/SPAN&gt; &lt;SPAN class="pl-smi"&gt;$v_helper_o365_ipv4cidr&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Query ::&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Could this be used to resolve domains related to Windows Updates to IPs &amp;amp; populate an exclusion group to enable split tunneling in this case as there doesn't&amp;nbsp;appear to be a feed to pull domains/address ranges from? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there another known solution for this requirement as possibly a common ask?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please let me know what you think here.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jun 2021 10:42:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunnel-URL-resolution-quot-IPaddressFeed2CheckPoint-quot/m-p/120732#M8459</guid>
      <dc:creator>ConorOB</dc:creator>
      <dc:date>2021-06-09T10:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: Split tunnel - URL resolution "IPaddressFeed2CheckPoint" script for windows updates</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunnel-URL-resolution-quot-IPaddressFeed2CheckPoint-quot/m-p/120794#M8460</link>
      <description>&lt;P&gt;First of all, I think the requirement to "route all traffic" is...untenable for a variety of reasons.&lt;BR /&gt;A better approach would be to have the appropriate controls on the Endpoint (Harmony Endpoint/Browse) so routing the traffic back to a headend isn't necessary.&lt;/P&gt;
&lt;P&gt;Having said that, I imagine this code could (with modifications, likely) also work for the purpose of creating an encryption domain.&lt;BR /&gt;The main thing is that the output must be IP addresses, since you have to create regular network/host objects.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jun 2021 23:16:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunnel-URL-resolution-quot-IPaddressFeed2CheckPoint-quot/m-p/120794#M8460</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-06-09T23:16:51Z</dc:date>
    </item>
  </channel>
</rss>

