<?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 Third party support in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187510#M563945</link>
    <description>&lt;P&gt;On top of the links provided take a peek at the ISE Resources links at the top of the 'Network Access Control' community forum as there are really good examples and guides there.&amp;nbsp; Also, for free tutorials for ISE config demos take a look at:&amp;nbsp;&lt;A href="http://labminutes.com/video/sec" target="_blank"&gt;Video: Security | Lab Minutes&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Am I understanding correctly that the switches just need to support&amp;nbsp;802.1X, or that need to support&amp;nbsp;802.1X and have RADIUS and TACACS integration built in?&lt;/P&gt;
&lt;P&gt;-Yes.&amp;nbsp; Devices will need to be able to support dot1x and radius.&amp;nbsp; Radius is used between the authenticator (switch) and ISE (authentication server).&amp;nbsp; Note there are specific licenses (Base) needed to support your typical AAA services.&lt;/P&gt;
&lt;P&gt;Do I also understand correctly that ICE can have exceptions for certain nodes and endpoints if there are compatibility issues, but any new devices added to those nodes, a bad actor or such would still be blocked by ICE?&lt;/P&gt;
&lt;P&gt;-Yes.&amp;nbsp; You will utilize your policy sets to steer policy and allow (authorize) good known clients onto the network.&amp;nbsp; Bad actors should not match any policies and hit the default policy which should be secured (deny access).&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Nov 2020 13:36:08 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2020-11-23T13:36:08Z</dc:date>
    <item>
      <title>ISE Third party support</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187411#M563940</link>
      <description>&lt;P&gt;Hi there, and thank you for reading.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Been out of IT infrastructure for a number of years and struggling to get up to speed rapidly.&lt;/P&gt;&lt;P&gt;Im looking at an existing ICE system supporting AAA/ Profiling/BTOD/Guest/Posture services.&lt;/P&gt;&lt;P&gt;We are looking to add some third party switch hardware and door access/cctv endpoints, which we want to be complient with ICE. Am I understanding correctly that the switches just need to support&amp;nbsp;802.1X, or that need to support&amp;nbsp;802.1X and have RADIUS and TACACS integration built in?&lt;/P&gt;&lt;P&gt;Do I also understand correctly that ICE can have exceptions for certain nodes and endpoints if there are compatibility issues, but any new devices added to those nodes, a bad actor or such would still be blocked by ICE?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks in Advance&lt;/P&gt;&lt;P&gt;Fraser&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 10:49:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187411#M563940</guid>
      <dc:creator>FraserJohnston62763</dc:creator>
      <dc:date>2020-11-23T10:49:49Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Third party support</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187450#M563942</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Check below link for examples :&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-documents/ise-third-party-nad-profiles-and-configs/ta-p/3648719" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-third-party-nad-profiles-and-configs/ta-p/3648719&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 12:12:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187450#M563942</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2020-11-23T12:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Third party support</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187476#M563944</link>
      <description>&lt;P&gt;here is the device matrix based on the version of ISE you running&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/security/identity-services-engine/products-device-support-tables-list.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/security/identity-services-engine/products-device-support-tables-list.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 12:48:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187476#M563944</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-11-23T12:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Third party support</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187510#M563945</link>
      <description>&lt;P&gt;On top of the links provided take a peek at the ISE Resources links at the top of the 'Network Access Control' community forum as there are really good examples and guides there.&amp;nbsp; Also, for free tutorials for ISE config demos take a look at:&amp;nbsp;&lt;A href="http://labminutes.com/video/sec" target="_blank"&gt;Video: Security | Lab Minutes&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Am I understanding correctly that the switches just need to support&amp;nbsp;802.1X, or that need to support&amp;nbsp;802.1X and have RADIUS and TACACS integration built in?&lt;/P&gt;
&lt;P&gt;-Yes.&amp;nbsp; Devices will need to be able to support dot1x and radius.&amp;nbsp; Radius is used between the authenticator (switch) and ISE (authentication server).&amp;nbsp; Note there are specific licenses (Base) needed to support your typical AAA services.&lt;/P&gt;
&lt;P&gt;Do I also understand correctly that ICE can have exceptions for certain nodes and endpoints if there are compatibility issues, but any new devices added to those nodes, a bad actor or such would still be blocked by ICE?&lt;/P&gt;
&lt;P&gt;-Yes.&amp;nbsp; You will utilize your policy sets to steer policy and allow (authorize) good known clients onto the network.&amp;nbsp; Bad actors should not match any policies and hit the default policy which should be secured (deny access).&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 13:36:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-third-party-support/m-p/4187510#M563945</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2020-11-23T13:36:08Z</dc:date>
    </item>
  </channel>
</rss>

