<?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 Cisco ise profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866398#M472522</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Trying to understand the profiling behaviour,could you please correct me if my understanding is incorrect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;IP phone connects to the network and get profiled by ise and refects in endpoint repository.now i moved the mac adress data base to a new folder and create a&amp;nbsp; authorizastion policy.&lt;/P&gt;&lt;P&gt;now i disconnect the ip phone and reconnect,will it get again reprofiled by plus license and show in endpoint repository or ise will skip the profiling 2nd time and just enforce the authorization policy.&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;md&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 19:06:27 GMT</pubDate>
    <dc:creator>munish.dhiman1</dc:creator>
    <dc:date>2020-02-21T19:06:27Z</dc:date>
    <item>
      <title>Cisco ise profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866398#M472522</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Trying to understand the profiling behaviour,could you please correct me if my understanding is incorrect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;IP phone connects to the network and get profiled by ise and refects in endpoint repository.now i moved the mac adress data base to a new folder and create a&amp;nbsp; authorizastion policy.&lt;/P&gt;&lt;P&gt;now i disconnect the ip phone and reconnect,will it get again reprofiled by plus license and show in endpoint repository or ise will skip the profiling 2nd time and just enforce the authorization policy.&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;md&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 19:06:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866398#M472522</guid>
      <dc:creator>munish.dhiman1</dc:creator>
      <dc:date>2020-02-21T19:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ise profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866779#M472523</link>
      <description>Just to clarify a few things here is an overview:&lt;BR /&gt;ISE collects attributes from device sensors (NADs). The attributes are used to profile your devices. There are several probes you can use (Radius, IP, DNS, Radius, etc.). The only time a plus license gets consumed in regard to profiling is if you use the profiled endpoint group as a authz condition in your policies. Re-profiling could occur if there has been a change or if you have enabled new profiles with different MCFs that your devices may match to depending on how they are setup. Good luck &amp;amp; HTH!</description>
      <pubDate>Mon, 03 Jun 2019 12:47:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866779#M472523</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-06-03T12:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ise profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866929#M472524</link>
      <description>this was brought up before and pointed to a possible defect depending on your release. please make sure you're running latest patch and if still a problem check through the TAC as well&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jun 2019 17:12:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866929#M472524</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-06-03T17:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ise profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866980#M472525</link>
      <description>Jason,&lt;BR /&gt;&lt;BR /&gt;This is not an issue, however trying to understand the expected behavior. As per the process ,ise process a request in following order&lt;BR /&gt;&lt;BR /&gt;Profiling___authntication_____posture____than enforcement/authorization...&lt;BR /&gt;So if i move the profiled endpoint from known endpoint folder to any other folder ,and when next time same endpoint connects to the network ,will it show as unknown and ise will profil it again before authentication?&lt;BR /&gt;Reason of asking this :&lt;BR /&gt;1. Well ,I have a MAB policy and authorization is based on OUI (aa:cc:dd).After MAB ,device is checked for the OUI configured in the policy and access provided.&lt;BR /&gt;How can I detect Mac spoofing in this case and send coa?&lt;BR /&gt;&lt;BR /&gt;2. I am thinking of using a combination of something like this. "If a mac start from aa:bb:cc and found in folder ABC ---provide vlans10.&lt;BR /&gt;But Now if someone spoofs the mac address he will also get full access.beacuse it's the same mac or starts with same oui. How can we prevent this,how profiling/plus license makes a difference here?&lt;BR /&gt;&lt;BR /&gt;BR,&lt;BR /&gt;MD&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jun 2019 18:19:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3866980#M472525</guid>
      <dc:creator>munish.dhiman1</dc:creator>
      <dc:date>2019-06-03T18:19:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ise profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3867041#M472526</link>
      <description>Check this out: &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-22/200973-configure-anomalous-endpoint-detection-a.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-22/200973-configure-anomalous-endpoint-detection-a.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This can aide in deterring spoofed macs. HTH!</description>
      <pubDate>Mon, 03 Jun 2019 20:13:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3867041#M472526</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-06-03T20:13:35Z</dc:date>
    </item>
  </channel>
</rss>

