<?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: Cisco ISE Device admin Authz rules query in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3832897#M474123</link>
    <description>&lt;P&gt;Well Prime is causing an authentication event on the NAS, so in reality it's not Prime's issue - you need to configure the NAS to first perform local auth, then TACACS.&amp;nbsp; But if the NAS will always do TACACS first and local user only if AAA is down, then you have no hope to avoid the AAA call.&amp;nbsp; You could put the use in the ISE Identity Group to avoid an AD/LDAP lookup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On Cisco WLC you can set the order to be LOCAL, then TACACS.&amp;nbsp; That would solve your issue. But it opens up a security issue because users can then bypass your TACACS server by creating their own accounts - and then TACACS doesn't log the commands,etc.&amp;nbsp; Bad practice. Avoid that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the issue is that you don't want to see these events in LiveLogs then you can enable a Collection Filter to remove the events from the Logs (and reports too).&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Administration -&amp;gt; System -&amp;gt; Logging -&amp;gt; Collection Filters&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="collection filet.PNG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/33655i4CA7652DC8773C1F/image-size/large?v=v2&amp;amp;px=999" role="button" title="collection filet.PNG" alt="collection filet.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Apr 2019 11:19:26 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2019-04-05T11:19:26Z</dc:date>
    <item>
      <title>Cisco ISE Device admin Authz rules query</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3832830#M474122</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a query regrading exclusion for Cisco Prime user request(auth/authz) to ISE nodes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;CU is having the Cisco Prime into network for monitoring/config change. Prime have the level 15 admin user which auth/authz on every network device(20K) and pull the required info that creates huge requests on ISE.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can be a way to exclude the specific user or Prime IP exclusion on ISE to proceed further for auth/authz requests to minimise the overhead.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 09:46:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3832830#M474122</guid>
      <dc:creator>sondevi</dc:creator>
      <dc:date>2019-04-05T09:46:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device admin Authz rules query</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3832897#M474123</link>
      <description>&lt;P&gt;Well Prime is causing an authentication event on the NAS, so in reality it's not Prime's issue - you need to configure the NAS to first perform local auth, then TACACS.&amp;nbsp; But if the NAS will always do TACACS first and local user only if AAA is down, then you have no hope to avoid the AAA call.&amp;nbsp; You could put the use in the ISE Identity Group to avoid an AD/LDAP lookup.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On Cisco WLC you can set the order to be LOCAL, then TACACS.&amp;nbsp; That would solve your issue. But it opens up a security issue because users can then bypass your TACACS server by creating their own accounts - and then TACACS doesn't log the commands,etc.&amp;nbsp; Bad practice. Avoid that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the issue is that you don't want to see these events in LiveLogs then you can enable a Collection Filter to remove the events from the Logs (and reports too).&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Administration -&amp;gt; System -&amp;gt; Logging -&amp;gt; Collection Filters&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="collection filet.PNG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/33655i4CA7652DC8773C1F/image-size/large?v=v2&amp;amp;px=999" role="button" title="collection filet.PNG" alt="collection filet.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 11:19:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3832897#M474123</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-04-05T11:19:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device admin Authz rules query</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3833974#M474192</link>
      <description>&lt;P&gt;Hi Arne,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for highlighting the use of Collection filter, can be a use case for CU for prime live logs filtering.&lt;/P&gt;
&lt;P&gt;WLC is not a case as CU using TACACS feature only. In this case, I am not sure if only prime user can be filtered as Local auth on NAD devices. more looking on ISE side, can be a way to filter prime user authentication and should not be entertained/directly bypassed for authorization requests.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2019 06:06:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3833974#M474192</guid>
      <dc:creator>sondevi</dc:creator>
      <dc:date>2019-04-08T06:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device admin Authz rules query</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3834195#M474193</link>
      <description>&lt;P&gt;I don't quite follow what you've just written.&amp;nbsp; But when you say "bypassed" then you surely mean "do not use TACACS at all".&amp;nbsp; If your NAS sends a TACACS request to ISE then there is no concept of bypassing.&amp;nbsp; ISE has to process the request.&amp;nbsp; You can chose to authenticate locally (ISE internal user) - that is the only "optimisation"you can do.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2019 12:47:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3834195#M474193</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-04-08T12:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Device admin Authz rules query</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3834341#M474194</link>
      <description>&lt;P&gt;Hi Arne, thanks for more input. was looking that can bypass specific username or not on ISE.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2019 15:56:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-device-admin-authz-rules-query/m-p/3834341#M474194</guid>
      <dc:creator>sondevi</dc:creator>
      <dc:date>2019-04-08T15:56:59Z</dc:date>
    </item>
  </channel>
</rss>

