<?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: TACACS+ and syslog server in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/tacacs-and-syslog-server/m-p/583070#M427244</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nathan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As usual its "horses for courses". If you are using a AAA server (such as ACS) to secure access to your routers - then the best practice is to log both session and command accounting to AAA also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In that way the ACS server will be logging both succesful and failed login/command authorisation attempts AND the session/command accounting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All this gets logged to standard CSV files for off-line processing in Excel or rather better... something like extraxi aaa-reports!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;syslog, on the other hand, is a fire and forget, non standard and somewhat arcane method of logging. Being UDP its "fire and forget" and therefore not as reliable as TACACS+&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SOX now effects most large co's and access to network infrastructure (&amp;amp; hence audit of) is becoming vital.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 May 2006 20:23:40 GMT</pubDate>
    <dc:creator>darpotter</dc:creator>
    <dc:date>2006-05-11T20:23:40Z</dc:date>
    <item>
      <title>TACACS+ and syslog server</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-and-syslog-server/m-p/583069#M427242</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I was wondering about logging and aaa accounting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I notice some networks will have a syslog server and a tacacs+ server with aaa accounting.   Is it best practices on a security perspective to configure a router to use a syslog server and a tacacs+ server using aaa accounting?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 21:34:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-and-syslog-server/m-p/583069#M427242</guid>
      <dc:creator>nathan</dc:creator>
      <dc:date>2019-03-10T21:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS+ and syslog server</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-and-syslog-server/m-p/583070#M427244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nathan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As usual its "horses for courses". If you are using a AAA server (such as ACS) to secure access to your routers - then the best practice is to log both session and command accounting to AAA also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In that way the ACS server will be logging both succesful and failed login/command authorisation attempts AND the session/command accounting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All this gets logged to standard CSV files for off-line processing in Excel or rather better... something like extraxi aaa-reports!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;syslog, on the other hand, is a fire and forget, non standard and somewhat arcane method of logging. Being UDP its "fire and forget" and therefore not as reliable as TACACS+&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SOX now effects most large co's and access to network infrastructure (&amp;amp; hence audit of) is becoming vital.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 May 2006 20:23:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-and-syslog-server/m-p/583070#M427244</guid>
      <dc:creator>darpotter</dc:creator>
      <dc:date>2006-05-11T20:23:40Z</dc:date>
    </item>
  </channel>
</rss>

