<?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: Updatable objects for Desktop Policy in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53716#M12263</link>
    <description>Can you explain your exact use case for this feature?</description>
    <pubDate>Fri, 17 May 2019 16:21:59 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2019-05-17T16:21:59Z</dc:date>
    <item>
      <title>Updatable objects for Desktop Policy</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53395#M12262</link>
      <description>&lt;P&gt;As we have updatable objects for Office 365 services in the R80.20 gateway policy, I would like to have the same possibility for the Desktop.&lt;/P&gt;&lt;P&gt;Any ideas on how to make the Desktop policy more flexible in that way?&lt;BR /&gt;Today we manually maintain a "static" group of O365 addresses, which reflects Microsoft´s listing.&lt;/P&gt;&lt;P&gt;Are there any new features related to this challenge to be released?&lt;/P&gt;&lt;P&gt;I would suggest some kind of "SD-WAN" functionality, which can prioritize traffic to go through either VPN or not.&lt;/P&gt;&lt;P&gt;Regards&lt;BR /&gt;Poul Erik&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2019 08:54:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53395#M12262</guid>
      <dc:creator>PEO</dc:creator>
      <dc:date>2019-05-14T08:54:20Z</dc:date>
    </item>
    <item>
      <title>Re: Updatable objects for Desktop Policy</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53716#M12263</link>
      <description>Can you explain your exact use case for this feature?</description>
      <pubDate>Fri, 17 May 2019 16:21:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53716#M12263</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-05-17T16:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: Updatable objects for Desktop Policy</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53981#M12264</link>
      <description>&lt;P&gt;The use case:&lt;/P&gt;&lt;P&gt;we like to have a "as tight and precise&amp;nbsp;as possible desktop policy".&lt;/P&gt;&lt;P&gt;some trafic must go to the datacenter by VPN, some goes to O365 directly&amp;nbsp;etc.&lt;/P&gt;&lt;P&gt;the desktop policy should need as little as possible maintenance, meaning flexible and actual as e.g. Microsoft changes its networks and services over time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For that, I think, support for updatable objects in the desktop policy could be first step.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards, Poul Erik&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2019 07:54:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/53981#M12264</guid>
      <dc:creator>PEO</dc:creator>
      <dc:date>2019-05-21T07:54:58Z</dc:date>
    </item>
    <item>
      <title>Re: Updatable objects for Desktop Policy</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/54046#M12265</link>
      <description>What about Internet-bound traffic (not O365-related) in your scenario?</description>
      <pubDate>Tue, 21 May 2019 15:32:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Updatable-objects-for-Desktop-Policy/m-p/54046#M12265</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-05-21T15:32:38Z</dc:date>
    </item>
  </channel>
</rss>

