<?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 ACS/ASA authentication for vpn access vs. console management access in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219686#M379120</link>
    <description>&lt;P&gt;I have an ACS 4.2 Server and an ASA 5540.  I have setup AnyConnect SSL VPN on the ASA and want to authenticate users using AAA tacacs+ authentication with the ACS and an external Windows AD database.  I have done this successfully.  I also want to use the ACS for authenticating SSH management sessions into the ASA.  I have setup a group in AD and on the ACS called VPNUSERS and NETADMINS.  The problem is, I want the VPN users to ONLY be able to authenticate for VPN but not have access to logging into the ASA CLI or ASDM.  The NETADMINS should be able to do both.  The question I have is how do I setup the VPNUSER group in ACS to have access to connect to the ASA for VPN but not for the management console?  It seems that if they can authenticate for vpn, they can also ssh the firewall which is what I want to prevent.     &lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 23:23:13 GMT</pubDate>
    <dc:creator>Joshua Engels</dc:creator>
    <dc:date>2019-03-10T23:23:13Z</dc:date>
    <item>
      <title>ACS/ASA authentication for vpn access vs. console management access</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219686#M379120</link>
      <description>&lt;P&gt;I have an ACS 4.2 Server and an ASA 5540.  I have setup AnyConnect SSL VPN on the ASA and want to authenticate users using AAA tacacs+ authentication with the ACS and an external Windows AD database.  I have done this successfully.  I also want to use the ACS for authenticating SSH management sessions into the ASA.  I have setup a group in AD and on the ACS called VPNUSERS and NETADMINS.  The problem is, I want the VPN users to ONLY be able to authenticate for VPN but not have access to logging into the ASA CLI or ASDM.  The NETADMINS should be able to do both.  The question I have is how do I setup the VPNUSER group in ACS to have access to connect to the ASA for VPN but not for the management console?  It seems that if they can authenticate for vpn, they can also ssh the firewall which is what I want to prevent.     &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 23:23:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219686#M379120</guid>
      <dc:creator>Joshua Engels</dc:creator>
      <dc:date>2019-03-10T23:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: ACS/ASA authentication for vpn access vs. console management</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219687#M379151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try using Network Access Restrictions (NAR)where you can restrict the administrative access on per device or on NDG basis.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By default user accounts from external database such as AD in ACS will get authenticated through telnet on network device or a AAA client which can be restricted by enabling NAR in ACS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case it should be VPNUSERS group in ACS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Mar 2009 08:07:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219687#M379151</guid>
      <dc:creator>sahmedshahcsd</dc:creator>
      <dc:date>2009-03-16T08:07:26Z</dc:date>
    </item>
    <item>
      <title>Re: ACS/ASA authentication for vpn access vs. console management</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219688#M379186</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Using network access restriction is the solution here. Please see this link,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please see this link,&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://cisco.com/en/US/products/sw/secursw/ps2086/products_white_paper09186a00801a8fd0.shtml" target="_blank"&gt;http://cisco.com/en/US/products/sw/secursw/ps2086/products_white_paper09186a00801a8fd0.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;~JG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Mar 2009 20:23:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-asa-authentication-for-vpn-access-vs-console-management/m-p/1219688#M379186</guid>
      <dc:creator>Jagdeep Gambhir</dc:creator>
      <dc:date>2009-03-16T20:23:26Z</dc:date>
    </item>
  </channel>
</rss>

