<?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: Clear Anomalous Behaviour in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937083#M456646</link>
    <description>&lt;P&gt;I think it can be an indicator that something may not be right and worth digging into a particular endpoint to make sure it is a real issue or not.&amp;nbsp; But I wouldn't trust it since it only fires in specific situations such as moving from phone to PC or vice versa.&amp;nbsp; And it has a bug where it marks something anomalous when the DHCP Class Identifier changes.&amp;nbsp; But it is normal for a Windows PC to present multiple DHCP Class Identifiers depending on what applications are installed.&amp;nbsp; For example, the PC will send the normal MSFT-5.0 Class Identifier for the OS but then if Skype is installed, it will send another DHCP Class Identifier for Skype that looks like "MSFT-UC-Client".&amp;nbsp; Some applications use the DHCP Class Identifier to locate resources like SIP servers, proxy configuration files, etc.&lt;/P&gt;&lt;P&gt;So if your environment only shows one or two anomalous endpoints here and there, then certainly dive in and investigate those machines.&amp;nbsp; But don't automatically assume it is bad behavior.&amp;nbsp; If you are seeing hundreds or thousands of anomalous machines, then it is likely because of a particular application.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Oct 2019 12:56:18 GMT</pubDate>
    <dc:creator>Colby LeMaire</dc:creator>
    <dc:date>2019-10-08T12:56:18Z</dc:date>
    <item>
      <title>Clear Anomalous Behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3936505#M456641</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm running ISE 2.4 Patch 10.&amp;nbsp; Besides deleting the mac address, is there another way to clear&amp;nbsp;&lt;SPAN&gt;Anomalous Behaviour for the device?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Brian Persaud&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Oct 2019 15:40:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3936505#M456641</guid>
      <dc:creator>BrianPersaud</dc:creator>
      <dc:date>2019-10-07T15:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: Clear Anomalous Behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3936668#M456643</link>
      <description>&lt;P&gt;There is no way that I am aware of other than deleting the endpoint.&amp;nbsp; From context visibility, you can export all endpoints to a CSV file.&amp;nbsp; Massage the CSV file back into the import format.&amp;nbsp; Delete the anomalous endpoints from ISE.&amp;nbsp; Import the CSV file to get the endpoints back.&amp;nbsp; You will lose profiling data but at least you can ensure that you don't lose any static assignments.&amp;nbsp; It would be nice if they put an option in to reset the Anomalous Behavior attribute.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Oct 2019 20:07:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3936668#M456643</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2019-10-07T20:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: Clear Anomalous Behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937066#M456645</link>
      <description>Hi Colby thanks for the info and for the tip as well. Just out of curiosity, how often do you use anomalous behaviour for deployments. For sure I know there is major security benefits with it but it is worth it operationally?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 08 Oct 2019 12:10:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937066#M456645</guid>
      <dc:creator>BrianPersaud</dc:creator>
      <dc:date>2019-10-08T12:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: Clear Anomalous Behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937083#M456646</link>
      <description>&lt;P&gt;I think it can be an indicator that something may not be right and worth digging into a particular endpoint to make sure it is a real issue or not.&amp;nbsp; But I wouldn't trust it since it only fires in specific situations such as moving from phone to PC or vice versa.&amp;nbsp; And it has a bug where it marks something anomalous when the DHCP Class Identifier changes.&amp;nbsp; But it is normal for a Windows PC to present multiple DHCP Class Identifiers depending on what applications are installed.&amp;nbsp; For example, the PC will send the normal MSFT-5.0 Class Identifier for the OS but then if Skype is installed, it will send another DHCP Class Identifier for Skype that looks like "MSFT-UC-Client".&amp;nbsp; Some applications use the DHCP Class Identifier to locate resources like SIP servers, proxy configuration files, etc.&lt;/P&gt;&lt;P&gt;So if your environment only shows one or two anomalous endpoints here and there, then certainly dive in and investigate those machines.&amp;nbsp; But don't automatically assume it is bad behavior.&amp;nbsp; If you are seeing hundreds or thousands of anomalous machines, then it is likely because of a particular application.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2019 12:56:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937083#M456646</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2019-10-08T12:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: Clear Anomalous Behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937406#M456648</link>
      <description>&lt;P&gt;Thanks I will definitely dig in some more to get to the bottom of it.&amp;nbsp; I will start with the DHCP identifier since they are indeed doing Skype for business&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2019 20:16:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/clear-anomalous-behaviour/m-p/3937406#M456648</guid>
      <dc:creator>BrianPersaud</dc:creator>
      <dc:date>2019-10-08T20:16:02Z</dc:date>
    </item>
  </channel>
</rss>

