<?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: best practices for logging in Security</title>
    <link>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47403#M13876</link>
    <description>&lt;P&gt;Thanks that worked great.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Feb 2013 21:38:46 GMT</pubDate>
    <dc:creator>jalfrey</dc:creator>
    <dc:date>2013-02-28T21:38:46Z</dc:date>
    <item>
      <title>best practices for logging</title>
      <link>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47401#M13874</link>
      <description>&lt;P&gt;I'm setting up logging with Sonicwall firewalls. They support syslog. Do I send it to syslog on a linux system or send it directly to splunk via a port? If I setup multiple firewalls to log the same instance and I use the system syslog do I separate the log files in the syslog configuration? &lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 19:50:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47401#M13874</guid>
      <dc:creator>jalfrey</dc:creator>
      <dc:date>2013-02-28T19:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: best practices for logging</title>
      <link>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47402#M13875</link>
      <description>&lt;P&gt;You can send your syslog events directly to Splunk. &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Data/Monitornetworkports"&gt;Just setup up a UDP input&lt;/A&gt; (default port 514 for syslog) or a non default port if you wish.&lt;/P&gt;

&lt;P&gt;You'll then be able to search and categorize your syslog events in Splunk based on which host (sonic firewall) they came from, or any other fields in the syslog event that identify the origin.You can also dynamically set the source and sourcetype or route the syslog events to different indexes when everything is coming in over the same UDP port using entrys in transforms.conf.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 20:01:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47402#M13875</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2013-02-28T20:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: best practices for logging</title>
      <link>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47403#M13876</link>
      <description>&lt;P&gt;Thanks that worked great.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 21:38:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47403#M13876</guid>
      <dc:creator>jalfrey</dc:creator>
      <dc:date>2013-02-28T21:38:46Z</dc:date>
    </item>
    <item>
      <title>Re: best practices for logging</title>
      <link>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47404#M13877</link>
      <description>&lt;P&gt;This may also be of interest: &lt;A href="http://wiki.splunk.com/Community:Best_Practice_For_Configuring_Syslog_Input"&gt;http://wiki.splunk.com/Community:Best_Practice_For_Configuring_Syslog_Input&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2013 17:12:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/best-practices-for-logging/m-p/47404#M13877</guid>
      <dc:creator>dshpritz</dc:creator>
      <dc:date>2013-03-01T17:12:13Z</dc:date>
    </item>
  </channel>
</rss>

