<?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: Identity Services Engine Remediation or Quarantine VLAN Help in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4572558#M573525</link>
    <description>&lt;P&gt;That sounds like a great solution! I will take a look into it.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Mar 2022 12:17:37 GMT</pubDate>
    <dc:creator>Alex Pfeil</dc:creator>
    <dc:date>2022-03-17T12:17:37Z</dc:date>
    <item>
      <title>Identity Services Engine Remediation or Quarantine VLAN Help</title>
      <link>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4571969#M573515</link>
      <description>&lt;P&gt;We currently have devices being removed from AD after a certain period of time and removed from ISE after a certain period of time. Sometimes, these devices need to be re-added to the domain and ISE. However, if they are not in ISE and not in the domain, they cannot get on the network to get back onto the domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our current workaround for wireless devices is to get on our guest network and then VPN and re-join to the domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The wired process is to remove 802.1X and MAB from the switchport configuration, re-join the computer to the domain, and then re-add the configuration to the switch.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to have an access-list that would get applied to a failed device which would allow it to be re-joined to the network without posing a high risk to the network. Does anybody have a security concern for the access-lists that are recommended today?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2022 19:48:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4571969#M573515</guid>
      <dc:creator>Alex Pfeil</dc:creator>
      <dc:date>2022-03-16T19:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Services Engine Remediation or Quarantine VLAN Help</title>
      <link>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4572014#M573516</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/293775"&gt;@Alex Pfeil&lt;/a&gt;&amp;nbsp;instead of removing dot1x from the switch port config you could use a CWA to force a user to be redirected to a Web portal to login, if successful push down a DACL which permits limited access to the network to rejoin the domain.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2022 20:31:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4572014#M573516</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-03-16T20:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: Identity Services Engine Remediation or Quarantine VLAN Help</title>
      <link>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4572558#M573525</link>
      <description>&lt;P&gt;That sounds like a great solution! I will take a look into it.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Mar 2022 12:17:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/identity-services-engine-remediation-or-quarantine-vlan-help/m-p/4572558#M573525</guid>
      <dc:creator>Alex Pfeil</dc:creator>
      <dc:date>2022-03-17T12:17:37Z</dc:date>
    </item>
  </channel>
</rss>

