<?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 Spoofing in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-spoofing/m-p/3528494#M540950</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nadeem, I suggest limiting access using VLAN or ACL for AP access. The ACL can be crafted to allow for APs to join the controller, which at minimum would include DHCP, DNS, and GRE to the controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hosuk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Feb 2016 17:53:14 GMT</pubDate>
    <dc:creator>howon</dc:creator>
    <dc:date>2016-02-08T17:53:14Z</dc:date>
    <item>
      <title>ISE - Profiling - MAC Address Spoofing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-spoofing/m-p/3528493#M540944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 14px;"&gt;Hi Experts,&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 14px;"&gt;My Customer has Profiling enabled on the Prod ISE deployment and are correctly profiling Aruba AP's using MAB not Dot1x as the auth method.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 14px;"&gt;Customer is concerned that if the MAC address of the AP's spoofed would it be used on any device linux/windows etc to gain access to the network.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 14px;"&gt;The probes that they have currently setup are DHCP,Radius.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Is there a way to avoid MAC Address Spoofing in the above scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nadeem&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2016 17:43:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-spoofing/m-p/3528493#M540944</guid>
      <dc:creator>nadeekha</dc:creator>
      <dc:date>2016-02-08T17:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Profiling - MAC Address Spoofing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-spoofing/m-p/3528494#M540950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nadeem, I suggest limiting access using VLAN or ACL for AP access. The ACL can be crafted to allow for APs to join the controller, which at minimum would include DHCP, DNS, and GRE to the controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hosuk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2016 17:53:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-mac-address-spoofing/m-p/3528494#M540950</guid>
      <dc:creator>howon</dc:creator>
      <dc:date>2016-02-08T17:53:14Z</dc:date>
    </item>
  </channel>
</rss>

