<?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: Objects based on AD domain info in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241184#M46794</link>
    <description>&lt;P&gt;In order to see identities from another AD server; you’d have to configure Identity Collector to poll that AD server.&lt;BR /&gt;This is because to associate a user with an IP, we need to see the Security Logs from AD showing the user login.&lt;BR /&gt;Also, there would need to be an LDAP Account Unit defined for the relevant LDAP Branch.&lt;BR /&gt;Whether the partner will give you the necessary access to do that is a separate question.&lt;/P&gt;</description>
    <pubDate>Fri, 14 Feb 2025 04:38:25 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2025-02-14T04:38:25Z</dc:date>
    <item>
      <title>Objects based on AD domain info</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241137#M46793</link>
      <description>&lt;P&gt;We have just created an AD trust with a partner company.&amp;nbsp; Their AD domain is called "trusted.local".&amp;nbsp; We use our local AD domain "trusting.local" on our CP gateways for identity awareness functionality.&lt;/P&gt;&lt;P&gt;I am looking for a way to identify end users in the "trusted.local" AD domain based on the UPN suffix "trusted.local".&amp;nbsp; Something akin to "*@trusted.local" - I then want to be able to put them in an object that can be used in gateway policy as a source or destination..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&amp;nbsp; Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2025 15:40:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241137#M46793</guid>
      <dc:creator>Waldo</dc:creator>
      <dc:date>2025-02-13T15:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: Objects based on AD domain info</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241184#M46794</link>
      <description>&lt;P&gt;In order to see identities from another AD server; you’d have to configure Identity Collector to poll that AD server.&lt;BR /&gt;This is because to associate a user with an IP, we need to see the Security Logs from AD showing the user login.&lt;BR /&gt;Also, there would need to be an LDAP Account Unit defined for the relevant LDAP Branch.&lt;BR /&gt;Whether the partner will give you the necessary access to do that is a separate question.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 04:38:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241184#M46794</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-02-14T04:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Objects based on AD domain info</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241215#M46797</link>
      <description>&lt;P&gt;Phoneboy explained it perfectly.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 15:08:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Objects-based-on-AD-domain-info/m-p/241215#M46797</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-02-14T15:08:55Z</dc:date>
    </item>
  </channel>
</rss>

