<?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: Cisco ISE Profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3865729#M24799</link>
    <description>So you should not need Anyconnect as it is not required for anomalous detection. One thing I would be cautious of is if you enable anomalous detection it is an all or nothing thing. Meaning you cannot tweak what it will use. I have asked if it has been road mapped, but have yet to hear. By default it will use the following to determine changes: Endpoint Policy DHCP Class ID NAS-Port-Type&lt;BR /&gt;Also, ISE will re-categorize devices if you deploy profiles with higher MCFs and devices hit and match on those instead of a Cisco out of the box defined profile.&lt;BR /&gt;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;HTH!&lt;BR /&gt;</description>
    <pubDate>Fri, 31 May 2019 12:39:23 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2019-05-31T12:39:23Z</dc:date>
    <item>
      <title>Cisco ISE Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3865678#M24798</link>
      <description>&lt;P&gt;Hi ,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to understand&amp;nbsp; how ISE will actively does the flowing.&lt;/P&gt;&lt;P&gt;Ability to Detect Anomalous Behavior of Endpoints&lt;BR /&gt;Cisco ISE protects your network from the illegitimate use of a MAC address by detecting the endpoints involved in MAC address spoofing and allows you to restrict the permission of the suspicious endpoints. The following options are available in the profiler configuration page:&lt;/P&gt;&lt;P&gt;Enable Anomalous Behavior Detection—Cisco ISE probes for data and checks for any contradictions to the existing data. If any contradictions are found, the&amp;nbsp;AnomalousBehavior&amp;nbsp;attribute is set to true and the corresponding endpoints are displayed in the Context Visibility page.&lt;BR /&gt;Enable Anomalous Behavior Enforcement—A CoA is issued if anomalous behavior is detected. The suspicious endpoints are reauthorized based on the authorization rules configured in the Profiler Configuration page.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Is any connect required for active anomaly detection. Because once a device is profiled and categorized, ISE will not re-categorized that device again untill removed from the database.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or&amp;nbsp;&lt;/P&gt;&lt;P&gt;ISE will always profile the device whenever it receive an authentication&amp;nbsp; request from the device.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;MD&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 10:35:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3865678#M24798</guid>
      <dc:creator>munish.dhiman1</dc:creator>
      <dc:date>2019-05-31T10:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3865729#M24799</link>
      <description>So you should not need Anyconnect as it is not required for anomalous detection. One thing I would be cautious of is if you enable anomalous detection it is an all or nothing thing. Meaning you cannot tweak what it will use. I have asked if it has been road mapped, but have yet to hear. By default it will use the following to determine changes: Endpoint Policy DHCP Class ID NAS-Port-Type&lt;BR /&gt;Also, ISE will re-categorize devices if you deploy profiles with higher MCFs and devices hit and match on those instead of a Cisco out of the box defined profile.&lt;BR /&gt;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;HTH!&lt;BR /&gt;</description>
      <pubDate>Fri, 31 May 2019 12:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-profiling/m-p/3865729#M24799</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-05-31T12:39:23Z</dc:date>
    </item>
  </channel>
</rss>

