<?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: Ethernet ghosting Cisco ISE bypass in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5244538#M594064</link>
    <description>&lt;P&gt;MACsec should solve the problem so the switch and endpoint have an encrypted session. &lt;A href="https://cs.co/ise-berg#macsec" target="_blank"&gt;https://cs.co/ise-berg#macsec&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This is hardware capability of the network device and the endpoint (or software with Cisco AnyConnect, now Secure Client) and has nothing to do with ISE since it is simply the AAA server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jan 2025 19:49:12 GMT</pubDate>
    <dc:creator>thomas</dc:creator>
    <dc:date>2025-01-07T19:49:12Z</dc:date>
    <item>
      <title>Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5240652#M593946</link>
      <description>&lt;P&gt;Dear Cisco ISE lover,&lt;BR /&gt;&lt;BR /&gt;Currently, I have testing lab for the scenario of&amp;nbsp;Ethernet ghost.&amp;nbsp;&lt;BR /&gt;That is the most concerns which we can leverage existing user for gather sensitive information, and command and control.&lt;BR /&gt;&lt;BR /&gt;What the another concerns related, if attacker can spoof the MAC address of legitimate user as notice attack can take benefit from existing session, then they can connect network without posture scan (This attacker machine no any Cisco secure Client agent).&lt;BR /&gt;&lt;BR /&gt;Note: We use EAP-TLS and EAP-FAST with Posture check compliant.&amp;nbsp;&lt;BR /&gt;Please share me the fix solution.&lt;BR /&gt;Thank you,&lt;/P&gt;</description>
      <pubDate>Wed, 25 Dec 2024 08:01:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5240652#M593946</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2024-12-25T08:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5240723#M593947</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;ISE / switch authenticated on a per port basis, so if port 1 has a user authenticated, only that mac address is allowed on port 1, and if another users spoof the mac address on port 2, they wont be allowed as only port1/mac1 is authorized. there is also features like anamolous behavior detection to detect if same mac address shows different attributes to block access.&lt;/P&gt;
&lt;P&gt;also, if the user is using a different port, then they have to go through a full EAP/posture authentication even if they do mac spoofing..&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-blogs/cisco-ise-and-anomalous-behavior-detection-how-it-works/ba-p/4700300" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/security-blogs/cisco-ise-and-anomalous-behavior-detection-how-it-works/ba-p/4700300&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;**Please rate as helpful if this was useful **&lt;/P&gt;</description>
      <pubDate>Wed, 25 Dec 2024 15:33:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5240723#M593947</guid>
      <dc:creator>ccieexpert</dc:creator>
      <dc:date>2024-12-25T15:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5240797#M593950</link>
      <description>&lt;P&gt;I think you can't catch my concerns well,&amp;nbsp;&lt;BR /&gt;Please refer to this link&amp;nbsp;&lt;A href="https://www.immunit.ch/blog/2022/10/26/ethernet-ghosting-nac-bypass/" target="_blank"&gt;https://www.immunit.ch/blog/2022/10/26/ethernet-ghosting-nac-bypass/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Dec 2024 02:45:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5240797#M593950</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2024-12-26T02:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5241086#M593956</link>
      <description>&lt;P&gt;you are right, most NAC solutions will allow this. But this means that needs a full physical compromise. If it is a user port, they will need access to the wall port . One thing that might help a bit is period authetnication and also periodic posture evaluation, just to verify the trusted machine is still there and active.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Dec 2024 23:37:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5241086#M593956</guid>
      <dc:creator>ccieexpert</dc:creator>
      <dc:date>2024-12-26T23:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5241096#M593957</link>
      <description>&lt;P&gt;Thank for your information,&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1481123"&gt;@ccieexpert&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;What if we have insider threat bring HUB into cooperate network, it is the most concerns.&amp;nbsp;&lt;BR /&gt;How to prevent or detect this kind of attack.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 01:55:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5241096#M593957</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2024-12-27T01:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5241210#M593958</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1481123"&gt;@ccieexpert&lt;/a&gt;&amp;nbsp; Do you have alternative solution to detect or resolve this bypass?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 11:24:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5241210#M593958</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2024-12-27T11:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet ghosting Cisco ISE bypass</title>
      <link>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5244538#M594064</link>
      <description>&lt;P&gt;MACsec should solve the problem so the switch and endpoint have an encrypted session. &lt;A href="https://cs.co/ise-berg#macsec" target="_blank"&gt;https://cs.co/ise-berg#macsec&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This is hardware capability of the network device and the endpoint (or software with Cisco AnyConnect, now Secure Client) and has nothing to do with ISE since it is simply the AAA server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 19:49:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ethernet-ghosting-cisco-ise-bypass/m-p/5244538#M594064</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2025-01-07T19:49:12Z</dc:date>
    </item>
  </channel>
</rss>

