<?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: ISE Profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832562#M474160</link>
    <description>Have you tried using a logical profile?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;-Tim</description>
    <pubDate>Thu, 04 Apr 2019 19:47:53 GMT</pubDate>
    <dc:creator>Timothy Abbott</dc:creator>
    <dc:date>2019-04-04T19:47:53Z</dc:date>
    <item>
      <title>ISE Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832364#M474158</link>
      <description>&lt;P&gt;I am attempting to use profiling for SDA printer identification.&amp;nbsp; Basically I have a global policy (SDA_Printer) that uses IP startswith XX.XX.XX.&amp;nbsp; I have created an profiled endpoint group based on this.&lt;/P&gt;&lt;P&gt;Then I am planning to create several child policies.&amp;nbsp; For example, one I am testing out is SDA_HP_Printer:&lt;/P&gt;&lt;P&gt;MAC OUI Equals Hewlett Packard&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My SDA HP printers are being profiled as SDA_HP_Printer as expected which means it hit on the parent &amp;amp; child profile condition checks.&amp;nbsp; I would like to roll the MACs from all the children profile hits into the high level parent policy endpoint group so I can then use the top level in authz policy conditions.&amp;nbsp; This is not working as I thought it would.&amp;nbsp; Please advise.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2019 14:59:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832364#M474158</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-04-04T14:59:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832562#M474160</link>
      <description>Have you tried using a logical profile?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;-Tim</description>
      <pubDate>Thu, 04 Apr 2019 19:47:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832562#M474160</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-04-04T19:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832657#M474162</link>
      <description>Not yet. It is on my radar to test tomorrow. Any suggestions on best way to use them?</description>
      <pubDate>Thu, 04 Apr 2019 23:05:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling/m-p/3832657#M474162</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-04-04T23:05:21Z</dc:date>
    </item>
  </channel>
</rss>

