<?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 Spliting RA VPN access between domain and non-domain PCs fo domain users in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Spliting-RA-VPN-access-between-domain-and-non-domain-PCs-fo/m-p/226349#M3233</link>
    <description>&lt;P&gt;Hi there!&lt;/P&gt;&lt;P&gt;I would like to split access for remote users (MAB, RA VPN, 2FA) into domain and non-domain. All users have only MS AD accounts, but they can connect via VPN from a domain or non-domain PC. Depending on whether the PC is in the domain or not, different resource should be available.&lt;/P&gt;&lt;P&gt;For example, if John Doe connects from a domain PC, he can access the [LAN1] resource. But if the same John Doe connects from a non-domain PC, he can access [LAN2].&lt;/P&gt;&lt;P&gt;Can you please tell me if you have such an implementation? If so, how stable is it?&lt;/P&gt;&lt;P&gt;I think all RA resources will be announced into VPN for all users, regardless of whether the PC is in the domain or not. And access to [LAN1] or [LAN2] will be determined by the FW policy, but now I don't understand how to write it....&lt;/P&gt;</description>
    <pubDate>Thu, 12 Sep 2024 08:51:44 GMT</pubDate>
    <dc:creator>EVSolovyev</dc:creator>
    <dc:date>2024-09-12T08:51:44Z</dc:date>
    <item>
      <title>Spliting RA VPN access between domain and non-domain PCs fo domain users</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Spliting-RA-VPN-access-between-domain-and-non-domain-PCs-fo/m-p/226349#M3233</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;&lt;P&gt;I would like to split access for remote users (MAB, RA VPN, 2FA) into domain and non-domain. All users have only MS AD accounts, but they can connect via VPN from a domain or non-domain PC. Depending on whether the PC is in the domain or not, different resource should be available.&lt;/P&gt;&lt;P&gt;For example, if John Doe connects from a domain PC, he can access the [LAN1] resource. But if the same John Doe connects from a non-domain PC, he can access [LAN2].&lt;/P&gt;&lt;P&gt;Can you please tell me if you have such an implementation? If so, how stable is it?&lt;/P&gt;&lt;P&gt;I think all RA resources will be announced into VPN for all users, regardless of whether the PC is in the domain or not. And access to [LAN1] or [LAN2] will be determined by the FW policy, but now I don't understand how to write it....&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 08:51:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Spliting-RA-VPN-access-between-domain-and-non-domain-PCs-fo/m-p/226349#M3233</guid>
      <dc:creator>EVSolovyev</dc:creator>
      <dc:date>2024-09-12T08:51:44Z</dc:date>
    </item>
    <item>
      <title>Re: Spliting RA VPN access between domain and non-domain PCs fo domain users</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Spliting-RA-VPN-access-between-domain-and-non-domain-PCs-fo/m-p/226390#M3234</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/1629"&gt;@EVSolovyev&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is came into my mind: you are able to determine in the in the Access role the machine(s):&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="machines.png" style="width: 785px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/27581i8C0BE6CDEB5DEE8F/image-size/large?v=v2&amp;amp;px=999" role="button" title="machines.png" alt="machines.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;EM&gt;Choose a &lt;STRONG&gt;group of machines&lt;/STRONG&gt;&amp;nbsp;(this represents the domain machines)&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt; if the user connects from a machine what is not a domain member (not in the choosen group)&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;the rule won't applies to it.&lt;/EM&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;EM&gt;This kind of handling 100% stable, as the Access policy. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;There was a same kind of topic recently, have a look at on it:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;A href="https://community.checkpoint.com/t5/General-Topics/Standalone-Remote-Access-VPN-Client-Posture-Checks/m-p/224806#M37429" target="_blank"&gt;https://community.checkpoint.com/t5/General-Topics/Standalone-Remote-Access-VPN-Client-Posture-Checks/m-p/224806#M37429&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Maybe the&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_RemoteAccessVPN_AdminGuide/Topics-VPNRG/Secure-Configuration-Verification-Advanced.htm" target="_self" rel="noopener noreferrer"&gt;Secure Configuration Verification - Advanced&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;can be useful in this situation.&lt;/P&gt;
&lt;P&gt;What if you check the logged in user is a DOMAIN user in the companies AD?&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="MCDropDownHead dropDownHead"&gt;&lt;A class="MCDropDownHotSpot dropDownHotspot MCDropDownHotSpot_ MCHotSpotImage" role="button" href="https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_RemoteAccessVPN_AdminGuide/Topics-VPNRG/Secure-Configuration-Verification-Advanced.htm#" target="_blank" rel="noopener noreferrer" aria-expanded="true" aria-controls="mc-dropdown-body1bf28320-dc31-4e45-843f-16749a003d6b"&gt;"Groupmonitor"&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV id="mc-dropdown-body1bf28320-dc31-4e45-843f-16749a003d6b" class="MCDropDownBody dropDownBody"&gt;
&lt;P&gt;This checks that the logged on user belongs to the expected domain user groups.&lt;/P&gt;
&lt;TABLE class="TableStyle-TP_Table_Dark_Header_and_Pattern" cellspacing="0"&gt;&lt;COLGROUP&gt;&lt;COL class="TableStyle-TP_Table_Dark_Header_and_Pattern-Column-Column_Style" /&gt;&lt;COL class="TableStyle-TP_Table_Dark_Header_and_Pattern-Column-Column_Style" /&gt;&lt;/COLGROUP&gt;
&lt;THEAD&gt;
&lt;TR class="TableStyle-TP_Table_Dark_Header_and_Pattern-Head-Header_Style"&gt;
&lt;TH class="TableStyle-TP_Table_Dark_Header_and_Pattern-HeadE-Column_Style-Header_Style" scope="col"&gt;
&lt;P&gt;Parameter&lt;/P&gt;
&lt;/TH&gt;
&lt;TH class="TableStyle-TP_Table_Dark_Header_and_Pattern-HeadD-Column_Style-Header_Style" scope="col"&gt;
&lt;P&gt;Description&lt;/P&gt;
&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR class="TableStyle-TP_Table_Dark_Header_and_Pattern-Body-White_Background"&gt;
&lt;TD class="TableStyle-TP_Table_Dark_Header_and_Pattern-BodyB-Column_Style-White_Background"&gt;
&lt;P&gt;&lt;CODE&gt;"builtin\&lt;SPAN class="mc-variable Vars_Other.tp_admin variable"&gt;administrator&lt;/SPAN&gt;" (false)&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD class="TableStyle-TP_Table_Dark_Header_and_Pattern-BodyA-Column_Style-White_Background"&gt;
&lt;P&gt;A name of a user group. The user must belong to this group for the machine configuration to be verified.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Akos&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 13:04:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Spliting-RA-VPN-access-between-domain-and-non-domain-PCs-fo/m-p/226390#M3234</guid>
      <dc:creator>AkosBakos</dc:creator>
      <dc:date>2024-09-12T13:04:57Z</dc:date>
    </item>
  </channel>
</rss>

