<?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 MAC-ADDRESS FILTERING ON REMOTE VPN in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/mac-address-filtering-on-remote-vpn/m-p/4952007#M1105491</link>
    <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;Is it possible to filter VPN remote access with mac-addresses as a second layer factor security in addition to username/password on FMC?&lt;/P&gt;&lt;P&gt;If yes, any ideas to approach this?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Wed, 01 Nov 2023 13:22:51 GMT</pubDate>
    <dc:creator>fmugambi</dc:creator>
    <dc:date>2023-11-01T13:22:51Z</dc:date>
    <item>
      <title>MAC-ADDRESS FILTERING ON REMOTE VPN</title>
      <link>https://community.cisco.com/t5/network-security/mac-address-filtering-on-remote-vpn/m-p/4952007#M1105491</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;Is it possible to filter VPN remote access with mac-addresses as a second layer factor security in addition to username/password on FMC?&lt;/P&gt;&lt;P&gt;If yes, any ideas to approach this?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2023 13:22:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mac-address-filtering-on-remote-vpn/m-p/4952007#M1105491</guid>
      <dc:creator>fmugambi</dc:creator>
      <dc:date>2023-11-01T13:22:51Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ADDRESS FILTERING ON REMOTE VPN</title>
      <link>https://community.cisco.com/t5/network-security/mac-address-filtering-on-remote-vpn/m-p/4952068#M1105496</link>
      <description>&lt;P&gt;Not easily. MAC address is a layer 2 artifact and the connection comes in only with layer 3/4 information (protocol, source and destination IP address and port).&lt;/P&gt;
&lt;P&gt;The only way we can see MAC address is via something like AnyConnect ID Extensions (ACIDEX) which are exposed when using an add-on security service like Cisco Identity Services Engine (ISE). It can technically be done within an ASA or FTD config (the latter when using FMC and DAP) but I have never seen it done in my experience dealing with literally hundred of customer VPNs. &lt;/P&gt;
&lt;P&gt;Reference: &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/anyconnect-secure-mobility-client/118944-technote-anyconnect-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/anyconnect-secure-mobility-client/118944-technote-anyconnect-00.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you want to add a second factor to your security, use a Multi-Factor Authentication (MFA) service like Cisco Duo.&lt;/P&gt;
&lt;P&gt;Or you could change from username/password to certificates as your authentication method. This requires a PKI though; which can be daunting to setup if you don't have one already. It's not that hard, just not something most network or security admins have experience doing.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2023 14:58:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mac-address-filtering-on-remote-vpn/m-p/4952068#M1105496</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2023-11-01T14:58:38Z</dc:date>
    </item>
  </channel>
</rss>

