<?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: How custom forward logs to syslog server in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72697#M41161</link>
    <description>&lt;P&gt;Under the log-forwarding profile you can change the severity.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Feb 2016 16:34:25 GMT</pubDate>
    <dc:creator>pankaku</dc:creator>
    <dc:date>2016-02-11T16:34:25Z</dc:date>
    <item>
      <title>How custom forward logs to syslog server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72695#M41159</link>
      <description>&lt;P&gt;We are sending all logs&amp;nbsp;from Palo to SIEM. How can we eliminate those of low or no value to us&amp;nbsp;(exp. Allow_TCP_End) to be sent to syslog server? The server fills up quickly and there's a large amount of logs that provide no insight during analysis; we would like to NOT forward such logs. In other words, how pick and choose which event logs to send to syslog server? Thank you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2016 16:27:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72695#M41159</guid>
      <dc:creator>Arezoo</dc:creator>
      <dc:date>2016-02-11T16:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: How custom forward logs to syslog server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72697#M41161</link>
      <description>&lt;P&gt;Under the log-forwarding profile you can change the severity.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2016 16:34:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72697#M41161</guid>
      <dc:creator>pankaku</dc:creator>
      <dc:date>2016-02-11T16:34:25Z</dc:date>
    </item>
    <item>
      <title>Re: How custom forward logs to syslog server</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72740#M41174</link>
      <description>&lt;P&gt;If you do not wish to log allowed sessions you can remove log forwarding from the rules that allow traffic.&lt;/P&gt;
&lt;P&gt;If you only wish to log detected viruses in allowed traffic for example you can create a log forwarding profile with no log forwarding under the traffic settings and enabled log forwarding under the Threat settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately we are quite limited when it comes to forwarding of system logs. Under &lt;STRONG&gt;Device &amp;gt; Log settings&lt;/STRONG&gt; you can only select the severity of the system logs that will be forwarded. Unfortunately you cannot change severity of a certain event (for example failed admin logon). The result of this is that you cannot tune which events you wish to forward and which you don't and you will always end up forwarding too many or too few events.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One possibility is to set up a syslog relay server where you filter syslog which is forwarded to SIEM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;LPM&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 07:06:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-custom-forward-logs-to-syslog-server/m-p/72740#M41174</guid>
      <dc:creator>mvidic</dc:creator>
      <dc:date>2016-02-12T07:06:20Z</dc:date>
    </item>
  </channel>
</rss>

