<?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: Profiling Practices of IoT devices in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/4928070#M584225</link>
    <description>&lt;P&gt;&lt;SPAN&gt;When DHCP probing isn't possible for IoT devices with static IPs, the ISE community employs alternative methods. These include analyzing network traffic using NetFlow, port scanning for open ports, MAC address lookups, behavior analysis, device databases, and manual profiling. Combining these techniques helps identify and profile IoT devices effectively.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 23 Sep 2023 06:47:41 GMT</pubDate>
    <dc:creator>shreyiot</dc:creator>
    <dc:date>2023-09-23T06:47:41Z</dc:date>
    <item>
      <title>Profiling Practices of IoT devices</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/3495018#M538059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a number of IoT sensors in our environment which needs to be profiled.&lt;/P&gt;&lt;P&gt;For IoT devices which have DHCP enabled we have managed to leverage DHCP option request patterns and create custom profiling policies.&lt;/P&gt;&lt;P&gt;However some sensors have been assigned static IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wanted to know what are the practices in terms of profiling IoT devices,sensors are being followed by the ISE community if DHCP probe is not available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also has anyone tried to use Netflow for profiling ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2016 07:38:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/3495018#M538059</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2016-08-03T07:38:45Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling Practices of IoT devices</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/3495019#M538060</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nothing specific to IoT. &lt;A href="http://www.cisco.com/c/dam/en/us/products/collateral/security/medical-nac-white-paper.pdf"&gt;Cisco Medical NAC&lt;/A&gt; could be a good read for you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2016 13:54:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/3495019#M538060</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-08-03T13:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling Practices of IoT devices</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/4928070#M584225</link>
      <description>&lt;P&gt;&lt;SPAN&gt;When DHCP probing isn't possible for IoT devices with static IPs, the ISE community employs alternative methods. These include analyzing network traffic using NetFlow, port scanning for open ports, MAC address lookups, behavior analysis, device databases, and manual profiling. Combining these techniques helps identify and profile IoT devices effectively.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Sep 2023 06:47:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-practices-of-iot-devices/m-p/4928070#M584225</guid>
      <dc:creator>shreyiot</dc:creator>
      <dc:date>2023-09-23T06:47:41Z</dc:date>
    </item>
  </channel>
</rss>

