<?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 MAC address - Elapsed time - MAC Spoofing in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557480#M518767</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-676464"&gt;Ability to Detect Anomalous Behavior of Endpoints&lt;/A&gt;&lt;SPAN style="font-size: 10pt;"&gt; is added in ISE 2.1.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Jan 2018 17:49:46 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2018-01-08T17:49:46Z</dc:date>
    <item>
      <title>ISE Profiling MAC address - Elapsed time - MAC Spoofing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557479#M518759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;In Cisco ISE 1.4, when the ISE profiles an endpoint and if the endpoint is disconnected after a while, will ISE retain the endpoint's MAC address in profiled database until unless it detects a change in the profiling information from same MAC address?.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is regarding a security breach happened in one of my ISE customer. When a laptop used a spoofed MAC address of a Cisco IP Phone, it got authorised as Cisco IP Phone. There was no DHCP helper address configured for data VLANs (only configured for voice VLANs), and we only use DHCP and RADIUS as probes for profiling.&lt;/P&gt;&lt;P&gt;Is it because ISE didn't detect a profile information change on the same MAC address, it used the historical profiling data and authorised the MAC address as Cisco IP Phone. It would be great if someone could confirm if this is correct or expected behaviour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;V Vinodh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2018 13:58:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557479#M518759</guid>
      <dc:creator>junk1</dc:creator>
      <dc:date>2018-01-08T13:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiling MAC address - Elapsed time - MAC Spoofing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557480#M518767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-676464"&gt;Ability to Detect Anomalous Behavior of Endpoints&lt;/A&gt;&lt;SPAN style="font-size: 10pt;"&gt; is added in ISE 2.1.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jan 2018 17:49:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557480#M518767</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-01-08T17:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiling MAC address - Elapsed time - MAC Spoofing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557481#M518771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to anomalous detection you should be educating your customer that any time you are using MAB authentication the spoofing of a profiled MAC address or the spoofing of the profiling criteria is always a risk.&amp;nbsp; Each profiled MAB class should have a DACL applied to limit access to the access required by that class.&amp;nbsp; If you spoof a phone.... congrats you got on the network but can only do phone functions.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jan 2018 22:34:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-elapsed-time-mac-spoofing/m-p/3557481#M518771</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-01-10T22:34:53Z</dc:date>
    </item>
  </channel>
</rss>

