<?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: Identity Awareness in VSX in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75442#M9411</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/1967"&gt;@Lari_Luoma&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;The use case is that I have a policy based on AD OU (e.g. Finance or HR) that is why I plan to use the IA blade.&lt;/P&gt;&lt;P&gt;You mean for example in my VS1 I enable IA but in VS2 IA is disable?&lt;/P&gt;&lt;P&gt;Another thing, when I deploy VSX, the dedicated management port is the one I use to register to the Smart Console as the VSX gateway and the internal interface of each VS is the one I use to enroll the VS in Smart Console. Is there's a way to create a sub-interface in the management port so that i can assign that management port sub-interface per VS?&lt;/P&gt;&lt;P&gt;For example, VS1 will have MGMT1.1 then VS2 MGMT1.2, is it possible?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 17 Feb 2020 09:50:24 GMT</pubDate>
    <dc:creator>CyberBreaker</dc:creator>
    <dc:date>2020-02-17T09:50:24Z</dc:date>
    <item>
      <title>Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75416#M9409</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;I've done enabling identity awareness in a standalone but not in a VSX environment. Is it possible in VSX? If possible, how the gateway communicate to the AD is it per VS basis?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2020 04:28:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75416#M9409</guid>
      <dc:creator>CyberBreaker</dc:creator>
      <dc:date>2020-02-17T04:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75421#M9410</link>
      <description>&lt;P&gt;Hi!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is your specific use case?&lt;/P&gt;
&lt;P&gt;In VSX you enable IA on each virtual system and most commands work in VS context as in regular gateway.&lt;/P&gt;
&lt;P&gt;Check the following:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk88520" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk88520&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2020 06:51:37 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75421#M9410</guid>
      <dc:creator>Lari_Luoma</dc:creator>
      <dc:date>2020-02-17T06:51:37Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75442#M9411</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/1967"&gt;@Lari_Luoma&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;The use case is that I have a policy based on AD OU (e.g. Finance or HR) that is why I plan to use the IA blade.&lt;/P&gt;&lt;P&gt;You mean for example in my VS1 I enable IA but in VS2 IA is disable?&lt;/P&gt;&lt;P&gt;Another thing, when I deploy VSX, the dedicated management port is the one I use to register to the Smart Console as the VSX gateway and the internal interface of each VS is the one I use to enroll the VS in Smart Console. Is there's a way to create a sub-interface in the management port so that i can assign that management port sub-interface per VS?&lt;/P&gt;&lt;P&gt;For example, VS1 will have MGMT1.1 then VS2 MGMT1.2, is it possible?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2020 09:50:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75442#M9411</guid>
      <dc:creator>CyberBreaker</dc:creator>
      <dc:date>2020-02-17T09:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75485#M9412</link>
      <description>Some clarifications on VSX are needed it seems.&lt;BR /&gt;All communications between VS's and management are done over the VSX Gateway IP, also called VS0, so the IP you set on a Virtual System does not need to be able to communicate with the management server nor with the SmartConsole.&lt;BR /&gt;Each VS can be turned on or off regarding Identity Awareness, so you decide if it is needed for that specific VS and you turn it on only for those who need it.</description>
      <pubDate>Mon, 17 Feb 2020 13:32:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75485#M9412</guid>
      <dc:creator>Maarten_Sjouw</dc:creator>
      <dc:date>2020-02-17T13:32:56Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75518#M9413</link>
      <description>Also LDAP communication is using VS0 per default.&lt;BR /&gt;If this needs to be changed, because VS0 is not able to reach the needed LDAP-Server, this behavior is controlled as described in the following SK: &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk44726&amp;amp;partition=Advanced&amp;amp;product=VSX%22" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk44726&amp;amp;partition=Advanced&amp;amp;product=VSX%22&lt;/A&gt;</description>
      <pubDate>Mon, 17 Feb 2020 18:32:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75518#M9413</guid>
      <dc:creator>Norbert_Bohusch</dc:creator>
      <dc:date>2020-02-17T18:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75770#M9414</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/1967"&gt;@Lari_Luoma&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Is the IA blade still supported even in VSX bridge mode for R80.x?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2020 15:29:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75770#M9414</guid>
      <dc:creator>CyberBreaker</dc:creator>
      <dc:date>2020-02-19T15:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75779#M9415</link>
      <description>&lt;P&gt;IA is &lt;STRONG&gt;not&lt;/STRONG&gt; supported in bridge mode VS.&lt;/P&gt;
&lt;P&gt;For more information take a look at the following SK.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk101371" target="_blank"&gt;https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk101371&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2020 16:59:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75779#M9415</guid>
      <dc:creator>Lari_Luoma</dc:creator>
      <dc:date>2020-02-19T16:59:36Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75780#M9416</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/1967"&gt;@Lari_Luoma&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thanks for the feedback.&amp;nbsp;&lt;/P&gt;&lt;P&gt;But it supports in non-VSX bridge mode right?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2020 17:08:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75780#M9416</guid>
      <dc:creator>CyberBreaker</dc:creator>
      <dc:date>2020-02-19T17:08:50Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Awareness in VSX</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75786#M9417</link>
      <description>&lt;P&gt;Yes, supported in gw mode&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2020 17:41:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Identity-Awareness-in-VSX/m-p/75786#M9417</guid>
      <dc:creator>Lari_Luoma</dc:creator>
      <dc:date>2020-02-19T17:41:22Z</dc:date>
    </item>
  </channel>
</rss>

