<?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 Device Administration Radius - authz profiles in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/device-administration-radius-authz-profiles/m-p/3858273#M472899</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we are planing to use ISE for device administration for a large scale sp-like customer. We are using free-radius and want to replace it with ISE.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a complex environment, therefore our goal is to keep policies as simple as possible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are about 10 different departments each with its own network admin team, which is divided in 5 different teams like security, switching, routing etc. Within these teams we will have privileges WRITE, READ and LIMITED. Additionally we have to differentiate in the authorisation profiles between several vendors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have to assign more then one authz result to a authz policy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the authz policy would be something like the attached screenshot.&lt;/P&gt;&lt;P&gt;&lt;IMG border="0" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG border="0" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So my question/concern is about authz profile:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Afaik when I have more then one authz profile assigned to a policy all attributes will be send to NAD. Would that have any impact on the NAD, when e.g. Cisco device receives radius attributes from other vendors.&lt;/LI&gt;&lt;LI&gt;Is there maybe a better approach to design policies? I want to avoid to multiply the set of authz policies (see screenshot) by the number of vendors?&lt;/LI&gt;&lt;LI&gt;Is there maybe a more intelligent approach where ISE chooses the authz profile which fits to the NAD? Maybe roadmap?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks in advance for your input.&lt;/P&gt;&lt;P&gt;Cengiz&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Untitled 4.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/36918iF1A9E5C4823B4D1F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Untitled 4.png" alt="Untitled 4.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 May 2019 12:30:16 GMT</pubDate>
    <dc:creator>Cengiz Savas</dc:creator>
    <dc:date>2019-05-17T12:30:16Z</dc:date>
    <item>
      <title>Device Administration Radius - authz profiles</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-radius-authz-profiles/m-p/3858273#M472899</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we are planing to use ISE for device administration for a large scale sp-like customer. We are using free-radius and want to replace it with ISE.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a complex environment, therefore our goal is to keep policies as simple as possible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are about 10 different departments each with its own network admin team, which is divided in 5 different teams like security, switching, routing etc. Within these teams we will have privileges WRITE, READ and LIMITED. Additionally we have to differentiate in the authorisation profiles between several vendors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have to assign more then one authz result to a authz policy.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the authz policy would be something like the attached screenshot.&lt;/P&gt;&lt;P&gt;&lt;IMG border="0" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG border="0" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So my question/concern is about authz profile:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Afaik when I have more then one authz profile assigned to a policy all attributes will be send to NAD. Would that have any impact on the NAD, when e.g. Cisco device receives radius attributes from other vendors.&lt;/LI&gt;&lt;LI&gt;Is there maybe a better approach to design policies? I want to avoid to multiply the set of authz policies (see screenshot) by the number of vendors?&lt;/LI&gt;&lt;LI&gt;Is there maybe a more intelligent approach where ISE chooses the authz profile which fits to the NAD? Maybe roadmap?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks in advance for your input.&lt;/P&gt;&lt;P&gt;Cengiz&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Untitled 4.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/36918iF1A9E5C4823B4D1F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Untitled 4.png" alt="Untitled 4.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 12:30:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-radius-authz-profiles/m-p/3858273#M472899</guid>
      <dc:creator>Cengiz Savas</dc:creator>
      <dc:date>2019-05-17T12:30:16Z</dc:date>
    </item>
    <item>
      <title>Re: Device Administration Radius - authz profiles</title>
      <link>https://community.cisco.com/t5/network-access-control/device-administration-radius-authz-profiles/m-p/3858476#M472904</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;UL&gt;
&lt;LI&gt;Afaik when I have more then one authz profile assigned to a policy all attributes will be send to NAD. Would that have any impact on the NAD, when e.g. Cisco device receives radius attributes from other vendors.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;This depends on the NADs -- whether NADs able to ignore the attributes they do not understand.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;UL&gt;
&lt;LI&gt;Is there maybe a better approach to design policies? I want to avoid to multiply the set of authz policies (see screenshot) by the number of vendors?&lt;/LI&gt;
&lt;LI&gt;Is there maybe a more intelligent approach where ISE chooses the authz profile which fits to the NAD? Maybe roadmap?&lt;/LI&gt;
&lt;/UL&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;If the RADIUS authorization profiles differing in the RADIUS vendor dictionaries used, then you may use NAD profiles and select the list of RADIUS vendor dictionaries available to a particular NAD profile. See &lt;SPAN&gt;&lt;A href="https://community.cisco.com/t5/security-documents/how-to-create-network-access-device-profiles-with-cisco-ise/ta-p/3631103" target="_blank"&gt;How To: Create Network Access Device Pr... - Cisco Community&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 16:56:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/device-administration-radius-authz-profiles/m-p/3858476#M472904</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-05-17T16:56:29Z</dc:date>
    </item>
  </channel>
</rss>

