<?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: Question on Easyconnect in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569269#M508979</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You’re mixing different modes incorrectly&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Easy connect is for wired use cases where customers don’t want to deploy a wired supplicant. It’s an easy way to start getting visibility and control with ISE. Still recommended to deploy 802.1x eventually as it’s more secure and recommended method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vlan change is not going to work correctly as this requires a supplicant to release renew the IP address. Recommendation would be to deploy segmentation using SGTs. You could use acls but they don’t scale that week compared to the tagging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About shutting down switch port, likely through a manual COA action. What is the use case? Why would you want to instead of changing tag or acl instead?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Disconnect user on vpn, not sure what you’re tying to do as easy connect doesn’t play with vpn and same with blocking user on ssid.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Jun 2018 15:19:37 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2018-06-15T15:19:37Z</dc:date>
    <item>
      <title>Question on Easyconnect</title>
      <link>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569268#M508978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Folks, i'm not very familiar yet with Easyconnect and it's limitations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Main question is, considering the below traditional remediation actions with 802.1x, can we do ALL of them with Easyconnect?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Shutdown on Switch port&lt;/P&gt;&lt;P&gt;- Change VLAN on port&lt;/P&gt;&lt;P&gt;- dACL on Port&lt;/P&gt;&lt;P&gt;- Disconnect user from VPN&lt;/P&gt;&lt;P&gt;- Block user on SSID with WLC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 15:09:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569268#M508978</guid>
      <dc:creator>mcavinat</dc:creator>
      <dc:date>2018-06-15T15:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Easyconnect</title>
      <link>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569269#M508979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You’re mixing different modes incorrectly&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Easy connect is for wired use cases where customers don’t want to deploy a wired supplicant. It’s an easy way to start getting visibility and control with ISE. Still recommended to deploy 802.1x eventually as it’s more secure and recommended method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vlan change is not going to work correctly as this requires a supplicant to release renew the IP address. Recommendation would be to deploy segmentation using SGTs. You could use acls but they don’t scale that week compared to the tagging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About shutting down switch port, likely through a manual COA action. What is the use case? Why would you want to instead of changing tag or acl instead?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Disconnect user on vpn, not sure what you’re tying to do as easy connect doesn’t play with vpn and same with blocking user on ssid.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 15:19:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569269#M508979</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-06-15T15:19:37Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Easyconnect</title>
      <link>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569270#M508980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;Jason, thanks and agreed.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;This is an RFP that I'm filling and basically for each of the above situations they ask if we can do it WITH .1x and WITHOUT. &lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Would you agree that TECHNICALLY by NOT .1x we could interpret that for RFP purposes MAB is a possibility and then we could say "yes" to all above? I was thinking easyconnect but as this is an RFP creativity is important&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 15:28:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569270#M508980</guid>
      <dc:creator>mcavinat</dc:creator>
      <dc:date>2018-06-15T15:28:04Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Easyconnect</title>
      <link>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569271#M508981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The following with mab?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Shutdown on Switch port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Change VLAN on port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes but not recommended&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- dACL on Port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Disconnect user from VPN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No such mechanism.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Block user on SSID with WLC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are ways with profiling groups, etc that’s possible I guess&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 15:48:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/question-on-easyconnect/m-p/3569271#M508981</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-06-15T15:48:25Z</dc:date>
    </item>
  </channel>
</rss>

