<?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: ISE endpoint identity groups in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528163#M572079</link>
    <description>&lt;P&gt;Great, so a higher order classification it is then.&lt;/P&gt;&lt;P&gt;It surprised me though that as a classification, an endpoint can not belong to more than one group,&lt;/P&gt;&lt;P&gt;and being that Profiled is one of the branches, when an endpoint is moved to GuestEndpoints, you "loose" its original type so to say.&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jan 2022 22:09:45 GMT</pubDate>
    <dc:creator>cgm</dc:creator>
    <dc:date>2022-01-07T22:09:45Z</dc:date>
    <item>
      <title>ISE endpoint identity groups</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528113#M572073</link>
      <description>&lt;P&gt;Hi, happy new year!&lt;/P&gt;&lt;P&gt;It used to be the case that profile type was not readily available to use in authorization policies, but that is no longer the case. So what is the current use case for identity groups ? Just a higher order classification ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;-Carlos&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 20:21:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528113#M572073</guid>
      <dc:creator>cgm</dc:creator>
      <dc:date>2022-01-07T20:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE endpoint identity groups</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528154#M572077</link>
      <description>&lt;P&gt;It allows for a lot more freedom when grouping endpoints. A good example of this is using endpoint identity groups for static whitelists, or using them for iPSK. In both these cases you can have multiple endpoint types that wouldn't share the same profile but need the same treatment from an authz perspective.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 21:59:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528154#M572077</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2022-01-07T21:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: ISE endpoint identity groups</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528163#M572079</link>
      <description>&lt;P&gt;Great, so a higher order classification it is then.&lt;/P&gt;&lt;P&gt;It surprised me though that as a classification, an endpoint can not belong to more than one group,&lt;/P&gt;&lt;P&gt;and being that Profiled is one of the branches, when an endpoint is moved to GuestEndpoints, you "loose" its original type so to say.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 22:09:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-endpoint-identity-groups/m-p/4528163#M572079</guid>
      <dc:creator>cgm</dc:creator>
      <dc:date>2022-01-07T22:09:45Z</dc:date>
    </item>
  </channel>
</rss>

