<?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 ASA cut-through proxy and ACS 5.3 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/asa-cut-through-proxy-and-acs-5-3/m-p/1955299#M186896</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RS,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi here is the guide that helps you configure the cut-through proxy from the ASA this is a good example:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/access_fwaaa.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/access_fwaaa.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When configuring the ACS portion you can use two methods: "Cisco ACS" downloadable access-lists, "Any Radius Server" downloadable access-lists (my favorite), or you can send the filter attribute which points the user to a defined acl on the ASA. Either way you choose, you will have to first create a network authorization profile which will have the radius attributes in the formats that are outlined in this guide. You will create an authorization policy that will call this authorization policy as the result when they meet this condition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know how things go, if you get stuck, please posts screenshots so I can help you further.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik admani&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Jul 2012 05:21:30 GMT</pubDate>
    <dc:creator>Tarik Admani</dc:creator>
    <dc:date>2012-07-17T05:21:30Z</dc:date>
    <item>
      <title>ASA cut-through proxy and ACS 5.3</title>
      <link>https://community.cisco.com/t5/network-access-control/asa-cut-through-proxy-and-acs-5-3/m-p/1955298#M186850</link>
      <description>&lt;P&gt;Hi, I'm planning to migrate a customer from ACS 4.2 to ACS 5.3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have migrated the configuration for all the services but I'm thinking how to configure ASA 8.4 cut-through proxy service in TACACS+.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The same ASA uses TACACS+ for device mngt and RADIUS for vpn remote-access services.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rs&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:18:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-cut-through-proxy-and-acs-5-3/m-p/1955298#M186850</guid>
      <dc:creator>r.spiandorello</dc:creator>
      <dc:date>2019-03-11T02:18:29Z</dc:date>
    </item>
    <item>
      <title>ASA cut-through proxy and ACS 5.3</title>
      <link>https://community.cisco.com/t5/network-access-control/asa-cut-through-proxy-and-acs-5-3/m-p/1955299#M186896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RS,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi here is the guide that helps you configure the cut-through proxy from the ASA this is a good example:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/access_fwaaa.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/access_fwaaa.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When configuring the ACS portion you can use two methods: "Cisco ACS" downloadable access-lists, "Any Radius Server" downloadable access-lists (my favorite), or you can send the filter attribute which points the user to a defined acl on the ASA. Either way you choose, you will have to first create a network authorization profile which will have the radius attributes in the formats that are outlined in this guide. You will create an authorization policy that will call this authorization policy as the result when they meet this condition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know how things go, if you get stuck, please posts screenshots so I can help you further.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik admani&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2012 05:21:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-cut-through-proxy-and-acs-5-3/m-p/1955299#M186896</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-07-17T05:21:30Z</dc:date>
    </item>
  </channel>
</rss>

