<?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 Security On Demand - distinguishing compliance policy per user group. in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Endpoint-Security-On-Demand-distinguishing-compliance-policy-per/m-p/37007#M13874</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pawel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes. ESOD is pushed to gateway but you can fine tune access related things with applying Mobile access rules by creating Native applications, Web applications. Also there is a way to do drive mapping and other things with Native applications. You can apply&amp;nbsp;to particular users or groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R76/CP_R76_Mobile_Access_WebAdmin/23024.htm#o23211"&gt;https://sc1.checkpoint.com/documents/R76/CP_R76_Mobile_Access_WebAdmin/23024.htm#o23211&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Mar 2018 11:20:22 GMT</pubDate>
    <dc:creator>Gaurav_Pandya</dc:creator>
    <dc:date>2018-03-22T11:20:22Z</dc:date>
    <item>
      <title>Endpoint Security On Demand - distinguishing compliance policy per user group.</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Endpoint-Security-On-Demand-distinguishing-compliance-policy-per/m-p/37006#M13873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any chance to distinguish ESOD "Compliance" per user or user group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only possibile option I am aware of is to apply a ESOD policy directly to GW properties. So the only way i do see at this particular time is to create VSX context to distinguish Remote Access users and place propert perimeter verification when trying to establish User2Site tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If You know better way, please educate me asap &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Mar 2018 10:10:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Endpoint-Security-On-Demand-distinguishing-compliance-policy-per/m-p/37006#M13873</guid>
      <dc:creator>Pawel_Topczewsk</dc:creator>
      <dc:date>2018-03-22T10:10:37Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint Security On Demand - distinguishing compliance policy per user group.</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Endpoint-Security-On-Demand-distinguishing-compliance-policy-per/m-p/37007#M13874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pawel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes. ESOD is pushed to gateway but you can fine tune access related things with applying Mobile access rules by creating Native applications, Web applications. Also there is a way to do drive mapping and other things with Native applications. You can apply&amp;nbsp;to particular users or groups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R76/CP_R76_Mobile_Access_WebAdmin/23024.htm#o23211"&gt;https://sc1.checkpoint.com/documents/R76/CP_R76_Mobile_Access_WebAdmin/23024.htm#o23211&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Mar 2018 11:20:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Endpoint-Security-On-Demand-distinguishing-compliance-policy-per/m-p/37007#M13874</guid>
      <dc:creator>Gaurav_Pandya</dc:creator>
      <dc:date>2018-03-22T11:20:22Z</dc:date>
    </item>
  </channel>
</rss>

