<?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: ACS Server 6.0 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74783#M9522</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi KK,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's how you do it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beginning with PIX software release 5.2, we can define access lists on the PIX, then apply them on a per-user basis based in the user profile on the server. TACACS+ requires authentication and authorization. RADIUS requires authentication only. In our example, we changed outbound authentication and authorization to TACACS+ and set up an access list on the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: Starting in PIX Version 6.0.1, if using RADIUS, the access-lists can also be implemented by entering the list in standard IETF RADIUS attribute 11 (Filter-Id) [CSCdt50422]. In this example, attribute 11 could be set to 115 in lieu of doing the vendor-specific "acl=115" verbiage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX Configuration&lt;/P&gt;&lt;P&gt;access-list 115 permit tcp any host 99.99.99.2 eq telnet&lt;/P&gt;&lt;P&gt;access-list 115 permit tcp any host 99.99.99.2 eq www&lt;/P&gt;&lt;P&gt;access-list 115 permit tcp any host 99.99.99.2 eq ftp&lt;/P&gt;&lt;P&gt;access-list 115 deny tcp any host 99.99.99.3 eq www&lt;/P&gt;&lt;P&gt;access-list 115 deny tcp any host 99.99.99.3 eq ftp&lt;/P&gt;&lt;P&gt;access-list 115 deny tcp any host 99.99.99.3 eq telnet &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CiscoSecure NT TACACS+&lt;/P&gt;&lt;P&gt;To add authorization to the PIX to control where the user can go with access lists, check shell/exec, check the Access control list box, and fill in the number (matches the access list number on the PIX). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CiscoSecure NT RADIUS&lt;/P&gt;&lt;P&gt;Radius/Cisco is the device-type. Our "pixa" user needs a username, a password, and a check and "acl=115" in the Cisco/Radius rectangular box where it says 009\001 AV-Pair (vendor-specific).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more info, see:  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Performing Authentication, Authorization, and Accounting of Users Through PIX Versions 5.2 and Later&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/atp52.html#pix-config" target="_blank"&gt;http://www.cisco.com/warp/public/110/atp52.html#pix-config&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 05 Oct 2002 22:44:59 GMT</pubDate>
    <dc:creator>jekrauss</dc:creator>
    <dc:date>2002-10-05T22:44:59Z</dc:date>
    <item>
      <title>ACS Server 6.0</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74782#M9520</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just read that downloadble ACL's do not work for VPN users  and that it only helps in passthrough authentication. The workaround solution was to define the ACL on the pix and send down the ACL number on the ACS server. I have been lookking through the various options and could not locate the option for assigning the ACL number . All I see is an option to assign downloadble ACLS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would appreciate it if you gys could help me out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Karthik Krishnamurthy&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:04:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74782#M9520</guid>
      <dc:creator>Karthik.Krishnamurthy</dc:creator>
      <dc:date>2020-02-21T18:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: ACS Server 6.0</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74783#M9522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi KK,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's how you do it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beginning with PIX software release 5.2, we can define access lists on the PIX, then apply them on a per-user basis based in the user profile on the server. TACACS+ requires authentication and authorization. RADIUS requires authentication only. In our example, we changed outbound authentication and authorization to TACACS+ and set up an access list on the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: Starting in PIX Version 6.0.1, if using RADIUS, the access-lists can also be implemented by entering the list in standard IETF RADIUS attribute 11 (Filter-Id) [CSCdt50422]. In this example, attribute 11 could be set to 115 in lieu of doing the vendor-specific "acl=115" verbiage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX Configuration&lt;/P&gt;&lt;P&gt;access-list 115 permit tcp any host 99.99.99.2 eq telnet&lt;/P&gt;&lt;P&gt;access-list 115 permit tcp any host 99.99.99.2 eq www&lt;/P&gt;&lt;P&gt;access-list 115 permit tcp any host 99.99.99.2 eq ftp&lt;/P&gt;&lt;P&gt;access-list 115 deny tcp any host 99.99.99.3 eq www&lt;/P&gt;&lt;P&gt;access-list 115 deny tcp any host 99.99.99.3 eq ftp&lt;/P&gt;&lt;P&gt;access-list 115 deny tcp any host 99.99.99.3 eq telnet &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CiscoSecure NT TACACS+&lt;/P&gt;&lt;P&gt;To add authorization to the PIX to control where the user can go with access lists, check shell/exec, check the Access control list box, and fill in the number (matches the access list number on the PIX). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CiscoSecure NT RADIUS&lt;/P&gt;&lt;P&gt;Radius/Cisco is the device-type. Our "pixa" user needs a username, a password, and a check and "acl=115" in the Cisco/Radius rectangular box where it says 009\001 AV-Pair (vendor-specific).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more info, see:  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Performing Authentication, Authorization, and Accounting of Users Through PIX Versions 5.2 and Later&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/atp52.html#pix-config" target="_blank"&gt;http://www.cisco.com/warp/public/110/atp52.html#pix-config&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Oct 2002 22:44:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74783#M9522</guid>
      <dc:creator>jekrauss</dc:creator>
      <dc:date>2002-10-05T22:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: ACS Server 6.0</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74784#M9523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks . I will definately try that today and will let you know if it worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Karthik.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Oct 2002 13:25:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-server-6-0/m-p/74784#M9523</guid>
      <dc:creator>Karthik.Krishnamurthy</dc:creator>
      <dc:date>2002-10-07T13:25:49Z</dc:date>
    </item>
  </channel>
</rss>

