<?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 Transitioning Through Profiles (Profile Stacking) in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452001#M569149</link>
    <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Version 3.0.0.458&lt;/P&gt;&lt;P&gt;Installed Patches 2&lt;/P&gt;&lt;P&gt;Product Identifier (PID) ISE-VM-K9&lt;/P&gt;&lt;P&gt;Version Identifier (VID) V01&lt;/P&gt;&lt;P&gt;ADE-OS Version 3.0.8.091&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question about “stacking” profiles. By stacking, I mean, I have setup ISE to NMAP and profile an factory new endpoint to an initially trusted endpoint profile and assign it to an identity group as a &lt;U&gt;candidate&lt;/U&gt; for further processing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The initial profile works great, the NMAP performs its scan, meeting a profiler policy condition through customized NMAPExtension and the system places the endpoint in a selected Identity Group called “candidate”.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Life would be so easy if I left the endpoint in this state, but I have this access requirement to first profile the endpoint and use a graduated approach from a candidate (member of this identity group) to a higher set of authorizations including VLAN/dACL assignment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My initial approach was to build a policy set outside of the initial working set that bought the “layer0-endpoint” to “layer1-candidate” and then once in the candidate stage, authorized it to a different authorization profile, turning it into “layer2-release”. Obviously, I am performing configurations to the endpoint when they transition through the phases – including an eventual DOT1X implementation in the end.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Goes from out of the factory sealed box and added to the network -&amp;nbsp;layer0-endpoint -&amp;gt; layer1-candidate -&amp;gt;&amp;nbsp;layer2-release&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ve tried a few things, yet nothing is working. At this point, I’m unsure it is even possible to first profile an endpoint into a candidate and then into release – or my profile stacking concept.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any points or artlicles which may help please…&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
    <pubDate>Thu, 19 Aug 2021 17:34:55 GMT</pubDate>
    <dc:creator>chris-lawrence</dc:creator>
    <dc:date>2021-08-19T17:34:55Z</dc:date>
    <item>
      <title>Transitioning Through Profiles (Profile Stacking)</title>
      <link>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452001#M569149</link>
      <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Version 3.0.0.458&lt;/P&gt;&lt;P&gt;Installed Patches 2&lt;/P&gt;&lt;P&gt;Product Identifier (PID) ISE-VM-K9&lt;/P&gt;&lt;P&gt;Version Identifier (VID) V01&lt;/P&gt;&lt;P&gt;ADE-OS Version 3.0.8.091&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a question about “stacking” profiles. By stacking, I mean, I have setup ISE to NMAP and profile an factory new endpoint to an initially trusted endpoint profile and assign it to an identity group as a &lt;U&gt;candidate&lt;/U&gt; for further processing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The initial profile works great, the NMAP performs its scan, meeting a profiler policy condition through customized NMAPExtension and the system places the endpoint in a selected Identity Group called “candidate”.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Life would be so easy if I left the endpoint in this state, but I have this access requirement to first profile the endpoint and use a graduated approach from a candidate (member of this identity group) to a higher set of authorizations including VLAN/dACL assignment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My initial approach was to build a policy set outside of the initial working set that bought the “layer0-endpoint” to “layer1-candidate” and then once in the candidate stage, authorized it to a different authorization profile, turning it into “layer2-release”. Obviously, I am performing configurations to the endpoint when they transition through the phases – including an eventual DOT1X implementation in the end.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Goes from out of the factory sealed box and added to the network -&amp;nbsp;layer0-endpoint -&amp;gt; layer1-candidate -&amp;gt;&amp;nbsp;layer2-release&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ve tried a few things, yet nothing is working. At this point, I’m unsure it is even possible to first profile an endpoint into a candidate and then into release – or my profile stacking concept.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any points or artlicles which may help please…&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Thu, 19 Aug 2021 17:34:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452001#M569149</guid>
      <dc:creator>chris-lawrence</dc:creator>
      <dc:date>2021-08-19T17:34:55Z</dc:date>
    </item>
    <item>
      <title>Re: Transitioning Through Profiles (Profile Stacking)</title>
      <link>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452637#M569187</link>
      <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So my question is not related to stacking profiles (I guess considered "reprofiling")... I suppose I want to create a new &lt;U&gt;policy set&lt;/U&gt; to apply to the&amp;nbsp;&lt;SPAN&gt;“layer1-candidate” after it has been given an&amp;nbsp;Identity Group Assignment to my group - and then once you become a member of that group, you get updated permissions (new VLAN/dACL) given the endpoint modified access.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I just do see how this is done with the Policy Set Conditions Studio. I just don't see a dictionary which allowes me to choose some of the ISE&amp;nbsp;parameters like the grouping the endpoint&amp;nbsp;belongs to or its currently assigned policy.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2021 17:40:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452637#M569187</guid>
      <dc:creator>chris-lawrence</dc:creator>
      <dc:date>2021-08-20T17:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Transitioning Through Profiles (Profile Stacking)</title>
      <link>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452961#M569196</link>
      <description>&lt;P&gt;Chris: You are correct that endpoint groups or attributes are not currently available as conditions to select a policy set. Thus, you would need to use the same policy set or key off others.&lt;/P&gt;</description>
      <pubDate>Sun, 22 Aug 2021 02:44:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/transitioning-through-profiles-profile-stacking/m-p/4452961#M569196</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2021-08-22T02:44:23Z</dc:date>
    </item>
  </channel>
</rss>

