<?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 Using AD-Host-Resolved-DNs in Profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588706#M520240</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working with a client who is doing PEAP Domain Computer and PEAP User + MAR Cache.&amp;nbsp; As the computer and user get authenticated ISE records the following under the endpoint:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; AD-Host-Resolved-DNs &lt;/P&gt;&lt;P&gt; AD-User-Resolved-DNs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyway I can use those values in profiling?&amp;nbsp; I can't find an option to.&amp;nbsp; I am trying to profile endpoints whose &lt;SPAN style="font-size: 13.3333px;"&gt;AD-Host-Resolved-DNs contain a particular OU.&amp;nbsp; In this case, I am trying to profile laptops vs. desktops based on the OU in AD.&amp;nbsp;&amp;nbsp; The customer has the laptops and desktops in different OUs.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;They only want to apply posturing rules to laptops, but because they are transitioning to User mode authentication I can't easily do that with authorization rules.&amp;nbsp; I am trying to see if I can combine profiling with authentication to say "If a user is authenticating from a device profiled as a laptop then apply the posturing logic."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Any thoughts on this.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Nov 2017 13:32:39 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2017-11-02T13:32:39Z</dc:date>
    <item>
      <title>Using AD-Host-Resolved-DNs in Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588706#M520240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working with a client who is doing PEAP Domain Computer and PEAP User + MAR Cache.&amp;nbsp; As the computer and user get authenticated ISE records the following under the endpoint:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; AD-Host-Resolved-DNs &lt;/P&gt;&lt;P&gt; AD-User-Resolved-DNs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anyway I can use those values in profiling?&amp;nbsp; I can't find an option to.&amp;nbsp; I am trying to profile endpoints whose &lt;SPAN style="font-size: 13.3333px;"&gt;AD-Host-Resolved-DNs contain a particular OU.&amp;nbsp; In this case, I am trying to profile laptops vs. desktops based on the OU in AD.&amp;nbsp;&amp;nbsp; The customer has the laptops and desktops in different OUs.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;They only want to apply posturing rules to laptops, but because they are transitioning to User mode authentication I can't easily do that with authorization rules.&amp;nbsp; I am trying to see if I can combine profiling with authentication to say "If a user is authenticating from a device profiled as a laptop then apply the posturing logic."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Any thoughts on this.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Nov 2017 13:32:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588706#M520240</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-11-02T13:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: Using AD-Host-Resolved-DNs in Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588707#M520242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello , i think you must create different&lt;/P&gt;&lt;P&gt;&lt;SPAN class="dijitTreeLabelFocused dijitTreeLabel" title="Profiling Policies"&gt;Profiling Policies &lt;/SPAN&gt;for laptops and desktops with different OU .In my deployment we have desktops with names like PC400123.ad.corp and notebooks NB400123.ad.corp .And all are resolvable by cmd with this names .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Nov 2017 14:05:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588707#M520242</guid>
      <dc:creator>ognyan.totev</dc:creator>
      <dc:date>2017-11-02T14:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Using AD-Host-Resolved-DNs in Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588708#M520248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Short answer is no.&amp;nbsp; You could submit feature enhancement with customer name and impact.&amp;nbsp; There are requests to extend attributes in Profiler, but helps to be specific as to which are needed for prioritization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We do not expose those particular attributes to profiler today but may be possible to achieve similar intent via AD Join Point, NMAP-SMB Domain, DHCP hostname/DDNS name, or possibly use GPO to set User Class ID to include OU.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scripting could also be used to fetch AD LDAP info and set custom attributes in ISE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once shift to user auth, not sure new endpoints will be populating the AD host info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Nov 2017 18:37:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588708#M520248</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2017-11-02T18:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: Using AD-Host-Resolved-DNs in Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588709#M520249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Craig.&amp;nbsp; That is what I thought.&amp;nbsp; I know I can do the DHCP class GPO trick, but was hoping to be able to use that attribute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the quick response.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Nov 2017 20:19:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/3588709#M520249</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-11-02T20:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: Using AD-Host-Resolved-DNs in Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/5152868#M590932</link>
      <description>&lt;P&gt;Hi! I'm in the same situation and I'd like to confirm if we're still in the state or if we can somehow check the AD-Host-Resolved-DNs value. We're using ISE 3.2 patch 6. Thx!&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 13:33:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/using-ad-host-resolved-dns-in-profiling/m-p/5152868#M590932</guid>
      <dc:creator>lecabral</dc:creator>
      <dc:date>2024-07-29T13:33:17Z</dc:date>
    </item>
  </channel>
</rss>

