<?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: profiled endpoint group based on location in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598354#M528665</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you could use RADIUS:NASID to identify the switch you initially connected to then use profiling exception action to statically assign it to an endpoint group.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Jul 2017 16:40:25 GMT</pubDate>
    <dc:creator>howon</dc:creator>
    <dc:date>2017-07-05T16:40:25Z</dc:date>
    <item>
      <title>profiled endpoint group based on location</title>
      <link>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598353#M528663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 15px;"&gt;Is it possible to place a profiled endpoint into a group based on where it was learned?&lt;/P&gt;&lt;P style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 15px;"&gt;For example, if a Printer was seen and profiled when attached to switch X, place it in the "Known Printers" endpoint group, which an Authorization Policy can reference. This will prevent just *any* printer from being allowed on the network via MAB if the Authentication Policy only references "internal endpoints" and there is no catch-all Authorization Policy to deny access.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jul 2017 16:28:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598353#M528663</guid>
      <dc:creator>barawlin</dc:creator>
      <dc:date>2017-07-05T16:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: profiled endpoint group based on location</title>
      <link>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598354#M528665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you could use RADIUS:NASID to identify the switch you initially connected to then use profiling exception action to statically assign it to an endpoint group.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jul 2017 16:40:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598354#M528665</guid>
      <dc:creator>howon</dc:creator>
      <dc:date>2017-07-05T16:40:25Z</dc:date>
    </item>
    <item>
      <title>Re: profiled endpoint group based on location</title>
      <link>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598355#M528667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For groups of NADs, recommend assign them to NDG.&amp;nbsp; You can then use NDG in Profile Condition.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jul 2017 13:33:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiled-endpoint-group-based-on-location/m-p/3598355#M528667</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2017-07-06T13:33:23Z</dc:date>
    </item>
  </channel>
</rss>

