<?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 / Tacacs and Failed Attempts in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225243#M7760</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I hear ya.&lt;/P&gt;&lt;P&gt;I know that acs 5 is going to be a lot more policy based on how users authenticate and what policies get applied depending on their location, etc... Hopefully the logging will offer some of the same granularity.&lt;/P&gt;&lt;P&gt;-Jesse&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Mar 2009 17:13:48 GMT</pubDate>
    <dc:creator>Jesse Wiener</dc:creator>
    <dc:date>2009-03-18T17:13:48Z</dc:date>
    <item>
      <title>ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225238#M7755</link>
      <description>&lt;P&gt;In our aaa implementation we use tacacs with the local db as backup. Well, I'm trying to harden security. I know IOS has this nice little command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;&amp;#156;login on-failure log every xâ&amp;#128;&amp;#157;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would be great so we could at least see the syslog message and have an idea if someone is trying to get into a piece of our equipment without having to try and watch the "Failed Attemps" report in ACS - but given we are using Tacacs, the only way this will throw a message is if ACS isn't available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd like to know if there is a way for ACS to give us this information.  Or, to get syslog messages to get thrown.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:23:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225238#M7755</guid>
      <dc:creator>soldnermichael</dc:creator>
      <dc:date>2020-02-21T18:23:07Z</dc:date>
    </item>
    <item>
      <title>Re: ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225239#M7756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can have acs push out to your syslog. &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.1/configuration/guide/syslog.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.1/configuration/guide/syslog.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 16:04:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225239#M7756</guid>
      <dc:creator>Jesse Wiener</dc:creator>
      <dc:date>2009-03-18T16:04:37Z</dc:date>
    </item>
    <item>
      <title>Re: ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225240#M7757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yep - I was just hoping for some more granularity since all of our wireless devices enterprise-wide authenticate against ACS.  I only want to know about the failed tacacs attempts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 16:19:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225240#M7757</guid>
      <dc:creator>soldnermichael</dc:creator>
      <dc:date>2009-03-18T16:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225241#M7758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So you only want to see syslog message for tacacs failures not for wireless auth failures. I am not sure how you would do that from ACS. &lt;/P&gt;&lt;P&gt;If it were me I would use a splunk syslog server and send all of the failures to it. Then in splunk I would setup a filter to only display the NAS-IP-Addresses that I was interested in.&lt;/P&gt;&lt;P&gt;Or if I had MARS I would setup a rule in that to look for login failures on those devices to trigger a notification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is your syslog server now?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 16:38:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225241#M7758</guid>
      <dc:creator>Jesse Wiener</dc:creator>
      <dc:date>2009-03-18T16:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225242#M7759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We currently use Orion.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess I was just hoping to keep it within that so we'd see the syslog come through, but using Splunk isn't a bad idea...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 16:45:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225242#M7759</guid>
      <dc:creator>soldnermichael</dc:creator>
      <dc:date>2009-03-18T16:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225243#M7760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I hear ya.&lt;/P&gt;&lt;P&gt;I know that acs 5 is going to be a lot more policy based on how users authenticate and what policies get applied depending on their location, etc... Hopefully the logging will offer some of the same granularity.&lt;/P&gt;&lt;P&gt;-Jesse&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 17:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225243#M7760</guid>
      <dc:creator>Jesse Wiener</dc:creator>
      <dc:date>2009-03-18T17:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: ACS / Tacacs and Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225244#M7761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guess I'm stuck then.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 17:27:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-tacacs-and-failed-attempts/m-p/1225244#M7761</guid>
      <dc:creator>soldnermichael</dc:creator>
      <dc:date>2009-03-18T17:27:40Z</dc:date>
    </item>
  </channel>
</rss>

