<?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 2.2 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777938#M541910</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;why wouldn't a different ACL on MAC endpoint group work?&amp;nbsp;Agree SGT is the way to go but if its only a small amount of users might not be worth the effort.VLAN change is crappy but there are already port macros..&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/solution-for-change-of-vlan-for-wired-guests-using-smart-port/td-p/3432614" target="_blank"&gt;https://community.cisco.com/t5/identity-services-engine-ise/solution-for-change-of-vlan-for-wired-guests-using-smart-port/td-p/3432614&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jan 2019 17:09:14 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2019-01-11T17:09:14Z</dc:date>
    <item>
      <title>Cisco ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777352#M541906</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we have cisco&amp;nbsp;ise 2.2, we have some critical devices in the network and we have profiled them. Everything is working fine. As the default nature for authentication on ise, if the end device cannot pass the authentication then it will go to the&amp;nbsp;Guest VLAN. And in the Guest VLAN, the endpoint can go on the internet. But this is common for all unauthenticated end devices.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But I want to configure it little different way for the critical devices. If the critical devices fail to authenticate then it will go on Guest VLAN that's okay but the critical devices should not go on the internet. How can I block only a few unauthenticated devices to get internet access from Guest VLAN?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in Advance!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:53:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777352#M541906</guid>
      <dc:creator>jm.virtual01</dc:creator>
      <dc:date>2019-03-11T08:53:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777353#M541907</link>
      <description>You would need to somehow identify those devices&lt;BR /&gt;&lt;BR /&gt;Simplest way would be to create an endpoint group with their Mac addresses and create a rule to say:&lt;BR /&gt;If mab and critics devices then return a different ACL that doesn’t allow internet &lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2019 02:01:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777353#M541907</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-01-11T02:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777355#M541908</link>
      <description>&lt;P&gt;I have already profiled them and it is working fine. But I do not know, how can I block it to get internet access from guest VLAN&amp;nbsp;once the authentication failed for those&amp;nbsp;endpoints.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 02:04:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777355#M541908</guid>
      <dc:creator>jm.virtual01</dc:creator>
      <dc:date>2019-01-11T02:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777356#M541909</link>
      <description>&lt;P&gt;I think this becomes a L3 issue and no longer authentication.&amp;nbsp; If you had TrustSec then it might be trivial because you could assign an SGT to this class of user and enforce a separate ACL on the Firewall.&lt;/P&gt;
&lt;P&gt;Perhaps the pragmatic approach is to put this class of user on a separate VLAN? At least then you have an IP source address range which you can use in your firewall/ACL rule set to block internet.&amp;nbsp; It would be the only identifier of this class of user that you have.&lt;/P&gt;
&lt;P&gt;A third technique could be to force users through a proxy and catch them there via another round of authentication.&amp;nbsp; But that is another world of pain that I assume you want to avoid.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 02:10:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777356#M541909</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-01-11T02:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777938#M541910</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;why wouldn't a different ACL on MAC endpoint group work?&amp;nbsp;Agree SGT is the way to go but if its only a small amount of users might not be worth the effort.VLAN change is crappy but there are already port macros..&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/solution-for-change-of-vlan-for-wired-guests-using-smart-port/td-p/3432614" target="_blank"&gt;https://community.cisco.com/t5/identity-services-engine-ise/solution-for-change-of-vlan-for-wired-guests-using-smart-port/td-p/3432614&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 17:09:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3777938#M541910</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-01-11T17:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3778066#M541911</link>
      <description>&lt;P&gt;Ah yes of course. You’re right&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199790"&gt;@Jason Kunst&lt;/a&gt;&amp;nbsp;a dynamic NAS ACL would take care of it. The client would have a default gateway, but the NAS ACL (e.g. WLC ACL ) acts as a L2 firewall and you could allow only RFC1918 subnets. That would effectively block internet&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jan 2019 20:51:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-2/m-p/3778066#M541911</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-01-11T20:51:19Z</dc:date>
    </item>
  </channel>
</rss>

