<?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: accounting for anyconnect users in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613467#M559706</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Gavin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You posted your question in the Firewalling section instead of the VPN section. That's probably why you haven't received any replies yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding your question: Yes, accounting for AnyConnect users is possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you only need to know when each AnyConnect user logs on and off, you only need to configure an accounting server group in the Connection Profile ("Tunnel Group" in the CLI) as explained here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/vpngrp.html#wp1062323"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/vpngrp.html#wp1062323&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further information on the "accounting-server-group" CLI command can be found here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/a1.html#wp1560638"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/a1.html#wp1560638&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you also need to know which TCP and UDP traffic each AnyConnect user passes through the tunnel, this can be done as well. Please find a configuration example here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b04552.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b04552.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Mar 2011 09:56:39 GMT</pubDate>
    <dc:creator>Michael Schueler</dc:creator>
    <dc:date>2011-03-28T09:56:39Z</dc:date>
    <item>
      <title>accounting for anyconnect users</title>
      <link>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613466#M559705</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can we do accounting for normal any connect users? i.e. accouting for anyone who is logged on to the network using anyconnect?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:08:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613466#M559705</guid>
      <dc:creator>gavin han</dc:creator>
      <dc:date>2019-03-11T20:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: accounting for anyconnect users</title>
      <link>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613467#M559706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Gavin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You posted your question in the Firewalling section instead of the VPN section. That's probably why you haven't received any replies yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding your question: Yes, accounting for AnyConnect users is possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you only need to know when each AnyConnect user logs on and off, you only need to configure an accounting server group in the Connection Profile ("Tunnel Group" in the CLI) as explained here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/vpngrp.html#wp1062323"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/vpngrp.html#wp1062323&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further information on the "accounting-server-group" CLI command can be found here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/a1.html#wp1560638"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/a1.html#wp1560638&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you also need to know which TCP and UDP traffic each AnyConnect user passes through the tunnel, this can be done as well. Please find a configuration example here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b04552.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080b04552.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2011 09:56:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613467#M559706</guid>
      <dc:creator>Michael Schueler</dc:creator>
      <dc:date>2011-03-28T09:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: accounting for anyconnect users</title>
      <link>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613468#M559707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks machael. so I will also be able to know which user did what?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2011 13:14:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accounting-for-anyconnect-users/m-p/1613468#M559707</guid>
      <dc:creator>gavin han</dc:creator>
      <dc:date>2011-03-30T13:14:37Z</dc:date>
    </item>
  </channel>
</rss>

