<?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: Parser View vs Privilege Level using AAA / TACACS Authorization in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/parser-view-vs-privilege-level-using-aaa-tacacs-authorization/m-p/4299577#M565817</link>
    <description>&lt;P&gt;The most common approach I see is using privilege levels with command authorisation via TACACS Command Sets and Profiles. See the &lt;A href="https://community.cisco.com/t5/security-documents/cisco-ise-device-administration-prescriptive-deployment-guide/ta-p/3738365#toc-hId-759088769" target="_blank" rel="noopener"&gt;Cisco ISE Device Administration Prescriptive Deployment Guide&lt;/A&gt; for examples on how you can do this with ISE. Any standards-based TACACS+ server should support the same functions, but you would need to test it.&lt;/P&gt;
&lt;P&gt;I've never used parser view, but it looks like it's possible to specify them in a TACACS Profile. This document uses CS-ACS, but you should be able to use the same approach in ISE or another T+ solution.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/create-role-based-cli-for-the-ios-router-and-link-it-with-users/ta-p/3136438" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/security-documents/create-role-based-cli-for-the-ios-router-and-link-it-with-users/ta-p/3136438&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 01 Mar 2021 21:32:23 GMT</pubDate>
    <dc:creator>Greg Gibbs</dc:creator>
    <dc:date>2021-03-01T21:32:23Z</dc:date>
    <item>
      <title>Parser View vs Privilege Level using AAA / TACACS Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/parser-view-vs-privilege-level-using-aaa-tacacs-authorization/m-p/4299520#M565814</link>
      <description>&lt;P&gt;Hell community,&lt;BR /&gt;&lt;BR /&gt;I am looking into Cisco's AAA implementation. Specifically, I want to implement role based access control integrated with TACACS Authorization for VTY Access. I am not interested in using local authentication.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have perused Cisco documentation and I have found there are two ways to implement this. One method makes use of the parser view. You can define a view and exclude or include commands from that view.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;Device(config)# parser view first inclusive
Device(config-view)# secret 5 firstpass
Device(config-view)# command exec exclude show version
Device(config-view)# command exec exclude configure terminal
Device(config-view)# command exec exclude all show ip
Device(config-view)# exit
Device(config)# parser view second
Device(config-view)# secret 5 secondpass
Device(config-view)# command exec include-exclusive show ip interface
Device(config-view)# command exec include logout
Device(config-view)# exit&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cfg/configuration/15-mt/sec-usr-cfg-15-mt-book/sec-role-base-cli.html#GUID-8CFFD65B-EE7E-41E0-92A5-35CACC7F4578" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cfg/configuration/15-mt/sec-usr-cfg-15-mt-book/sec-role-base-cli.html#GUID-8CFFD65B-EE7E-41E0-92A5-35CACC7F4578&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The second method is to define privilege levels and and move commands from one privilege level to another. By default, Cisco device come with&amp;nbsp; privilege levels 0, 1 and 15 by&amp;nbsp; default. Which means a network admin can define levels 2-14 and assign different commands there.&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;Device(config)# enable secret level level password
Device(config)# privilege exec level level command-string
Device(config)# privilege exec all level level command-string&lt;/PRE&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cfg/configuration/15-mt/sec-usr-cfg-15-mt-book/sec-cfg-sec-4cli.html#GUID-3D5E3E28-99F1-4061-BE6C-DE8BF66C0C9F" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cfg/configuration/15-mt/sec-usr-cfg-15-mt-book/sec-cfg-sec-4cli.html#GUID-3D5E3E28-99F1-4061-BE6C-DE8BF66C0C9F&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The Cisco documentation is pretty good in explaining how the privilege levels and parser views function on the Cisco device, but what I am specifically interested in is to integrate this with AAA for TACACS authorization.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Which method can be used to implement role based access control on a TACACS server: privilege levels, parser views or both ? And if so, how ? Is it dependent on the capabilities of the TACACS server itself ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 19:14:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/parser-view-vs-privilege-level-using-aaa-tacacs-authorization/m-p/4299520#M565814</guid>
      <dc:creator>chira.cipri@gmail.com</dc:creator>
      <dc:date>2021-03-01T19:14:34Z</dc:date>
    </item>
    <item>
      <title>Re: Parser View vs Privilege Level using AAA / TACACS Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/parser-view-vs-privilege-level-using-aaa-tacacs-authorization/m-p/4299577#M565817</link>
      <description>&lt;P&gt;The most common approach I see is using privilege levels with command authorisation via TACACS Command Sets and Profiles. See the &lt;A href="https://community.cisco.com/t5/security-documents/cisco-ise-device-administration-prescriptive-deployment-guide/ta-p/3738365#toc-hId-759088769" target="_blank" rel="noopener"&gt;Cisco ISE Device Administration Prescriptive Deployment Guide&lt;/A&gt; for examples on how you can do this with ISE. Any standards-based TACACS+ server should support the same functions, but you would need to test it.&lt;/P&gt;
&lt;P&gt;I've never used parser view, but it looks like it's possible to specify them in a TACACS Profile. This document uses CS-ACS, but you should be able to use the same approach in ISE or another T+ solution.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/create-role-based-cli-for-the-ios-router-and-link-it-with-users/ta-p/3136438" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/security-documents/create-role-based-cli-for-the-ios-router-and-link-it-with-users/ta-p/3136438&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 21:32:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/parser-view-vs-privilege-level-using-aaa-tacacs-authorization/m-p/4299577#M565817</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2021-03-01T21:32:23Z</dc:date>
    </item>
  </channel>
</rss>

