<?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 Anomalous Behavior Exclusions in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/anomalous-behavior-exclusions/m-p/3853925#M473207</link>
    <description>&lt;P&gt;I am running into a situation where I have some WDS PXE endpoints in my environment that are triggering the anomalous behavior flag. Reviewing the logs in ISE shows that the DHCP class-id changes from MSFT 5.0 to PXEClient; I am assuming when they reboot. Is there a way to exclude endpoints from being flagged as anomalous behavior? I am running ISE 2.6, and don't see much in terms of configuration except for a check box to enable; documentation doesn't show any additional options either.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 10 May 2019 13:42:36 GMT</pubDate>
    <dc:creator>Daniel Lucas</dc:creator>
    <dc:date>2019-05-10T13:42:36Z</dc:date>
    <item>
      <title>Anomalous Behavior Exclusions</title>
      <link>https://community.cisco.com/t5/network-access-control/anomalous-behavior-exclusions/m-p/3853925#M473207</link>
      <description>&lt;P&gt;I am running into a situation where I have some WDS PXE endpoints in my environment that are triggering the anomalous behavior flag. Reviewing the logs in ISE shows that the DHCP class-id changes from MSFT 5.0 to PXEClient; I am assuming when they reboot. Is there a way to exclude endpoints from being flagged as anomalous behavior? I am running ISE 2.6, and don't see much in terms of configuration except for a check box to enable; documentation doesn't show any additional options either.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2019 13:42:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/anomalous-behavior-exclusions/m-p/3853925#M473207</guid>
      <dc:creator>Daniel Lucas</dc:creator>
      <dc:date>2019-05-10T13:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: Anomalous Behavior Exclusions</title>
      <link>https://community.cisco.com/t5/network-access-control/anomalous-behavior-exclusions/m-p/3854023#M473208</link>
      <description>&lt;P&gt;actually its hard to find a work around on this since,&lt;/P&gt;
&lt;P&gt;the anomalous detection uses only 3 things&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;nas-port-type, class ID for dhcp and endpoint policy change.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;these parameters are not configurable, maybe we can address this for enhancement to give the admin more control on the conditions for&amp;nbsp; anomalous detection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2019 15:48:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/anomalous-behavior-exclusions/m-p/3854023#M473208</guid>
      <dc:creator>yalbikaw</dc:creator>
      <dc:date>2019-05-10T15:48:30Z</dc:date>
    </item>
  </channel>
</rss>

