<?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: Cisco ISE Device Profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4915842#M583830</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1196021"&gt;@jitendrac&lt;/a&gt;&amp;nbsp;Please check out the Cisco or 3rd-party solutions that Greg indicated above. Usually the solution will profile the endpoints and then share the data with ISE via pxGrid context-in.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Sep 2023 04:19:37 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2023-09-01T04:19:37Z</dc:date>
    <item>
      <title>Cisco ISE Device Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914113#M583716</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;Is there any list available where we can see which built-in device profiles are supported in the ISE 3.2 or 3.3 version? For example which Medical Devices,&amp;nbsp; IOT Devices, and Industrial control systems Profiles are supported?&lt;/P&gt;
&lt;P&gt;Also is there any limitation on the number of default device profiles that can be imported and used in the device profile policy?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 17:46:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914113#M583716</guid>
      <dc:creator>jitendrac</dc:creator>
      <dc:date>2023-08-29T17:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914255#M583725</link>
      <description>&lt;P&gt;I have not seen this list published anywhere, the only option I'm aware of is to go to the ISE deployment itself, or a Dcloud instance such as this 3.2 instant on.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://dcloud2-sjc.cisco.com/content/instantdemo/cisco-identity-services-engine-ise-3-2-instant-demo-preview?returnPathTitleKey=content-view" target="_blank"&gt;https://dcloud2-sjc.cisco.com/content/instantdemo/cisco-identity-services-engine-ise-3-2-instant-demo-preview?returnPathTitleKey=content-view&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;As far as a limitation and scaling for the number of endpoint profiles, I'm not aware of that number being published for any supported release. The old medical profile library page indicated no more than 2000 had been tested.&amp;nbsp;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/cisco-ise-medical-nac-profile-library-v2-0/ta-p/3638736#:~:text=The%20maximum%20number%20of%20profiles,2.1%20and%20above%20is%202000" target="_blank"&gt;https://community.cisco.com/t5/security-knowledge-base/cisco-ise-medical-nac-profile-library-v2-0/ta-p/3638736#:~:text=The%20maximum%20number%20of%20profiles,2.1%20and%20above%20is%202000&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 23:25:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914255#M583725</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2023-08-29T23:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914277#M583728</link>
      <description>&lt;P&gt;Just to add to Damien's response... while ISE has limited capability for profiling Medical, IoT, and Industrial IoT endpoints due to the limited information provided by the network, ISE integrates with multiple other Cisco and 3rd-party vendor solutions (e.g. Medigate, Ordr, CyberVision, Nozomi, and many others) that can provide more details to ISE that can be used as matching conditions in Authorization Profiles.&lt;/P&gt;
&lt;P&gt;For more information, see&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/products/security/identity-services-engine/technology-partners.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/products/security/identity-services-engine/technology-partners.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 01:46:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914277#M583728</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2023-08-30T01:46:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914490#M583737</link>
      <description>&lt;P&gt;Hi Thanks for information,&lt;/P&gt;
&lt;P&gt;i can see that there is an option to&amp;nbsp;Download the Medical NAC library ZIP file and then import it is cisco&amp;nbsp;Work Centers &amp;gt; Profiler &amp;gt; Profiling Policies&lt;BR /&gt;&lt;BR /&gt;just wanted to know from where we can download Medical Type of devices NAC library or OT specific NAC library. Will i have to ask respective OEM ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 11:08:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914490#M583737</guid>
      <dc:creator>jitendrac</dc:creator>
      <dc:date>2023-08-30T11:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914505#M583739</link>
      <description>&lt;P&gt;Ok I think i got where i should look&amp;nbsp;&lt;BR /&gt;"The Feed Service Partner Portal".&lt;/P&gt;
&lt;P&gt;I hope our partner's login request will get approved to access it and to contribution&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 11:34:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4914505#M583739</guid>
      <dc:creator>jitendrac</dc:creator>
      <dc:date>2023-08-30T11:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device Profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4915842#M583830</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1196021"&gt;@jitendrac&lt;/a&gt;&amp;nbsp;Please check out the Cisco or 3rd-party solutions that Greg indicated above. Usually the solution will profile the endpoints and then share the data with ISE via pxGrid context-in.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 04:19:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-profiling/m-p/4915842#M583830</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2023-09-01T04:19:37Z</dc:date>
    </item>
  </channel>
</rss>

