<?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: Endpoint client policy updates in Endpoint</title>
    <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/59673#M1411</link>
    <description>I've never heard of anyone doing this before.&lt;BR /&gt;I suppose it's no different than just opening up the Endpoint Server from the Internet.&lt;BR /&gt;That said, the NAT rules would be normally be configured in the policy, and thus the client and server would be aware of it.&lt;BR /&gt;They wouldn't necessarily be in this reverse proxy case, and that could be problematic.&lt;BR /&gt;&lt;BR /&gt;In any case, the Policy Server is the canonical supported way to do it.</description>
    <pubDate>Mon, 05 Aug 2019 19:13:37 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2019-08-05T19:13:37Z</dc:date>
    <item>
      <title>Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/58272#M1409</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a customer who has a central NPM/EPM server (R77.30) to manage their firewall and endpoint estate. They have an additional Endpoint Security Policy Server which faces the internet for clients in the field, and this works okay.&lt;/P&gt;&lt;P&gt;I was wondering if by putting a reverse proxy (e.g. NGINX) in front of the private EPM, we could in R80 replace the functionality of the current policy server, to save on support costs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jamie&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2019 15:13:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/58272#M1409</guid>
      <dc:creator>stallwoodj</dc:creator>
      <dc:date>2019-07-15T15:13:05Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/59673#M1411</link>
      <description>I've never heard of anyone doing this before.&lt;BR /&gt;I suppose it's no different than just opening up the Endpoint Server from the Internet.&lt;BR /&gt;That said, the NAT rules would be normally be configured in the policy, and thus the client and server would be aware of it.&lt;BR /&gt;They wouldn't necessarily be in this reverse proxy case, and that could be problematic.&lt;BR /&gt;&lt;BR /&gt;In any case, the Policy Server is the canonical supported way to do it.</description>
      <pubDate>Mon, 05 Aug 2019 19:13:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/59673#M1411</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-08-05T19:13:37Z</dc:date>
    </item>
  </channel>
</rss>

