<?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: Is there any way to prevent new MAC to be added to internal endpoi in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786269#M580206</link>
    <description>&lt;P&gt;&lt;SPAN&gt;What I want is using a trusted switch as an onboarding platform to learn new MAC and add these MAC to a trusted ID group, keep them in that group. Later, these MAC would connect to other switches, as they already included in that ID group, they can be authorized and access the network.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 03 Mar 2023 00:49:07 GMT</pubDate>
    <dc:creator>EHNET</dc:creator>
    <dc:date>2023-03-03T00:49:07Z</dc:date>
    <item>
      <title>Is there any way to prevent new MAC to be added to internal endpoints</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786141#M580182</link>
      <description>&lt;P&gt;We are trying to using MAB and existing internal endpoints as a whitelist ( I know it is not secure enough) to prevent new mac to access network. So I want anything that is not in internal endpoint to be rejected at authentication phase.&lt;/P&gt;&lt;P&gt;Is there anyway to achieve this ? I tried to remove a mac from internal endpoint, but ISE will automatically add it back after it reconnected.&lt;/P&gt;&lt;P&gt;I also know that I can achieve same goal by using authorization and putting trusted MAC into an ID group then use this group as condition. But the problem is how to auto add new MAC into this ID group ? Is there anyway to set conditions, for example any new MAC learnt from a specific named NAD to be added into this group? This is a dynamic environment, manually adding MAC into group is not feasible.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What I want is using a trusted switch as an onboarding platform to learn new MAC and add these MAC to a trusted ID group, keep them in that group. Later, these MAC would connect to other switches, as they already included in that ID group, they can be authorized and access the network.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;My interface config is as follows:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;device-tracking attach-policy ISE_Track&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;ip access-group ACL-DEFAULT in&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication control-direction in&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication event server alive action reinitialize&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication host-mode multi-auth&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication order mab&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication priority mab&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication port-control auto&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication periodic&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication timer reauthenticate server&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication timer inactivity server dynamic&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;authentication violation restrict&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;mab&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 18:43:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786141#M580182</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-03T18:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786145#M580183</link>
      <description>&lt;P&gt;Why not reject at authorization phase?&amp;nbsp; Accomplishes the same thing.&amp;nbsp; What exactly are you trying to do?&amp;nbsp; Just MAB only? Are&amp;nbsp; your "trusted" MAC addresses in an Endpoint ID Group?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Endpoint Purge rules could satisfy what you are trying to accomplish.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:18:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786145#M580183</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T19:18:40Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786147#M580184</link>
      <description>&lt;P&gt;you can add MAC entries in to ISE and create a profile, so only MAC address will be allowed, rest will be rejected.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:21:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786147#M580184</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-03-02T19:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786151#M580185</link>
      <description>&lt;P&gt;Thanks for the reply. We just want to use whitelisted MAC as NAC, that's it. And designate a trust device to add new mac to internal endpoint.&lt;/P&gt;&lt;P&gt;I know I can do this at authorization with trusted id group.&amp;nbsp; But how do I auto populate this group ? Besides manually importing ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:25:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786151#M580185</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T19:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786156#M580186</link>
      <description>&lt;P&gt;sorry, can you please elaborate more ? Do you mean assign trusted mac into&amp;nbsp; an id group ?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:32:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786156#M580186</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T19:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786157#M580187</link>
      <description>&lt;P&gt;Create Endpoint ID group.&amp;nbsp; Add MAC addresses to Endpoint ID Group.&amp;nbsp; Specify Endpoint ID group as a condition in the Authorization policy, passing the necessary attributes.&amp;nbsp; Set Default Authz policy to deny.&lt;/P&gt;
&lt;P&gt;Use profiling if you don't want to manually add each MAC address to the group.&amp;nbsp; Also prevents some MAC spoofing attempts too.&amp;nbsp; Required Advantage Licensing.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:36:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786157#M580187</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T19:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786162#M580188</link>
      <description>&lt;P&gt;Thanks a lot. I already know the first portion that you mentioned.&lt;/P&gt;&lt;P&gt;So I can using profiling to let a trusted NAD as a source to populate that ID group ?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:44:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786162#M580188</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T19:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786163#M580189</link>
      <description>&lt;P&gt;No.&amp;nbsp; Profiling is endpoint condition specific.&amp;nbsp; So ISE will authenticate/authorize anything that looks like a printer, AP, thin client, or whatever.&amp;nbsp; No static MAC address lists needed.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/ise-profiling-design-guide/ta-p/3739456" target="_blank"&gt;https://community.cisco.com/t5/security-knowledge-base/ise-profiling-design-guide/ta-p/3739456&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 19:48:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786163#M580189</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T19:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786171#M580190</link>
      <description>&lt;P&gt;So looks like you cant use properties from network device such as location or name in the profiling process&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 20:18:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786171#M580190</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T20:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786173#M580191</link>
      <description>&lt;P&gt;I mean you can use the NAD properties in the Authorization policies to give differentiated access.&amp;nbsp; What exactly are you trying to solve?&amp;nbsp; If a device is trusted (profiled, 802.1X, Static endpoint ID group, etc.) why does it matter what NAD the endpoint is connected to?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 20:23:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786173#M580191</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T20:23:02Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786185#M580192</link>
      <description>&lt;P&gt;I updated my description in my post. I want to just use MAC as the only source to control access. Because there are tons device types in our network, using profiling adds too much overhead to operation. So I want to use mac whitelist here, but that list need to be auto populated&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 20:52:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786185#M580192</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T20:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786190#M580193</link>
      <description>&lt;P&gt;Auto populate?&amp;nbsp; What would be your source of truth?&amp;nbsp; What would determine whether or not a device should be trusted?&amp;nbsp; What is your concern with profiling "overhead"?&amp;nbsp; Profiling removes the need for you to manually manage Static Endpoint ID Groups.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 20:59:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786190#M580193</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T20:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786194#M580194</link>
      <description>&lt;P&gt;That's what I am asking if this is doable in ISE. Something like putting a device in a device group, any new mac learned from the NAD in this group will be added into a trusted ID group.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 21:01:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786194#M580194</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T21:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786196#M580195</link>
      <description>&lt;P&gt;It's clear by now that ISE will "collect" every MAC address of every endpoint from Switches/WLC/VPN that send their RADIUS requests to ISE. That's how ISE populates its Context Visibility Database. ISE has no idea which of these endpoints are important to you. That decision can be done "automatically" by profiling (assigning endpoints to certain profiles of interest, e.g. printers, Windows-10 PCs, etc.) or manually - the manual method involves either clicking around in ISE Context Visibility and setting the Endpoint Profiles or even the Endpoint Identity Group - but it's a very laborious&amp;nbsp;process. You can also export the Endpoint database, and do this manipulation in a spreadhseet. Or, if you're clever enough, do it via REST API. Either way, there has to be some logic/reasoning applied that a machine can understand if you want this association to happen. Profiling is your best bet.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 21:04:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786196#M580195</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2023-03-02T21:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786200#M580197</link>
      <description>But why? What makes this particular NAD trustworthy? What stops someone from plugging anything into this particular NAD? What about other NADs in your environment?&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Mar 2023 21:09:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786200#M580197</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T21:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786211#M580198</link>
      <description>&lt;P&gt;Because we could have control who can plug anything into this trust NAD.&lt;/P&gt;&lt;P&gt;Existing MAC will be imported into an ID group.&lt;/P&gt;&lt;P&gt;Any new MAC that is not in the ID group will be rejected.&lt;/P&gt;&lt;P&gt;Only new MAC that learnt from this NAD will be auto added into this ID group( This's what I am asking if this doable)&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 21:17:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786211#M580198</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-02T21:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786218#M580199</link>
      <description>&lt;P&gt;Then why deploy NAC at all if you can 100% guarantee that your NADs have trusted devices?&amp;nbsp; Or is it just this one NAD?&amp;nbsp; Also plugging into one specific NAD is enough of a criteria to quantify device trust?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 21:37:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786218#M580199</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-03-02T21:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786233#M580202</link>
      <description>&lt;P&gt;How about creating a new Profiling Condition?&amp;nbsp; Use the NAS IP Address for the condition&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CharlieMoreton_0-1677793554509.png" style="width: 939px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/177943i20F6ED46BCBBA842/image-dimensions/939x453?v=v2" width="939" height="453" role="button" title="CharlieMoreton_0-1677793554509.png" alt="CharlieMoreton_0-1677793554509.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And then add a new Profiling Policy&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CharlieMoreton_1-1677794267334.png" style="width: 941px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/177944i04FE155B273F43E8/image-dimensions/941x595?v=v2" width="941" height="595" role="button" title="CharlieMoreton_1-1677794267334.png" alt="CharlieMoreton_1-1677794267334.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Have fun with Randomized MAC Addresses &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 21:58:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786233#M580202</guid>
      <dc:creator>Charlie Moreton</dc:creator>
      <dc:date>2023-03-02T21:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786267#M580205</link>
      <description>&lt;P&gt;Thanks for your suggestion. I guess the method here can assign MAC to an ID group when it is connected to that specific switch. But when the same MAC connects to another switch. That MAC wont be in that ID group any more.&lt;/P&gt;&lt;P&gt;What I want is using a trusted switch as an onboarding platform to learn new MAC and add these MAC to a trusted ID group, keep them in that group. Later, these MAC would connect to other switches, as they already included in that ID group, they can be authorized and access the network.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 00:47:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786267#M580205</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-03T00:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way to prevent new MAC to be added to internal endpoi</title>
      <link>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786269#M580206</link>
      <description>&lt;P&gt;&lt;SPAN&gt;What I want is using a trusted switch as an onboarding platform to learn new MAC and add these MAC to a trusted ID group, keep them in that group. Later, these MAC would connect to other switches, as they already included in that ID group, they can be authorized and access the network.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 00:49:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/is-there-any-way-to-prevent-new-mac-to-be-added-to-internal/m-p/4786269#M580206</guid>
      <dc:creator>EHNET</dc:creator>
      <dc:date>2023-03-03T00:49:07Z</dc:date>
    </item>
  </channel>
</rss>

