<?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: TLS syslog to a cloud based SIEM in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307538#M79877</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/131179"&gt;@ryupapa&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm assuming that the TLS syslog server and profile is setup correctly seeing that it's getting the config type logs just fine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You should be able to configure upto 4 servers in a single profile... I don't see why it wouldn't work.&lt;/P&gt;
&lt;P&gt;Does it work if you add ONLY the TLS syslog server into the new profile ? Or is it a problem only when you add multiple servers to the profile ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-Kiwi.&lt;/P&gt;
&lt;DIV id="ConnectiveDocSignExtentionInstalled" data-extension-version="1.0.4"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
    <pubDate>Wed, 22 Jan 2020 09:44:38 GMT</pubDate>
    <dc:creator>kiwi</dc:creator>
    <dc:date>2020-01-22T09:44:38Z</dc:date>
    <item>
      <title>TLS syslog to a cloud based SIEM</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307481#M79855</link>
      <description>&lt;P&gt;Running software version&amp;nbsp;&amp;nbsp;&lt;SPAN class="s1"&gt;8.1.10 on this PA firewall.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I have the TLS syslog server profile setup in Configuration type logs and that works (getting config logs).&lt;BR /&gt;Then I setup this log forwarder profile that has both TLS syslog and UDP syslog server profiles.&lt;BR /&gt;When using adding logging for each line of policy to log on session close with the aforementioned log forwarding profile. Only my UDP syslog collector is getting logs.&lt;BR /&gt;&lt;BR /&gt;Anyone else have any challenges getting this working?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2020 21:59:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307481#M79855</guid>
      <dc:creator>ryupapa</dc:creator>
      <dc:date>2020-01-21T21:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: TLS syslog to a cloud based SIEM</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307538#M79877</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/131179"&gt;@ryupapa&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm assuming that the TLS syslog server and profile is setup correctly seeing that it's getting the config type logs just fine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You should be able to configure upto 4 servers in a single profile... I don't see why it wouldn't work.&lt;/P&gt;
&lt;P&gt;Does it work if you add ONLY the TLS syslog server into the new profile ? Or is it a problem only when you add multiple servers to the profile ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-Kiwi.&lt;/P&gt;
&lt;DIV id="ConnectiveDocSignExtentionInstalled" data-extension-version="1.0.4"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 22 Jan 2020 09:44:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307538#M79877</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2020-01-22T09:44:38Z</dc:date>
    </item>
    <item>
      <title>Re: TLS syslog to a cloud based SIEM</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307574#M79881</link>
      <description>&lt;P&gt;Originally I had only the TLS syslog server. For fun I made a new log-profile. Still is not working.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I was toying with the idea that Palo just doesn't want to overburden themselves with TLS syslog for traffic logs. Doesn't make sense since it is documented.....&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 13:45:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307574#M79881</guid>
      <dc:creator>ryupapa</dc:creator>
      <dc:date>2020-01-22T13:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: TLS syslog to a cloud based SIEM</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307621#M79896</link>
      <description>&lt;P&gt;Looking at packet captures...&lt;BR /&gt;&lt;BR /&gt;the firewall establishes 3 way handshake with the SIEM for tls syslog. Waits for 106 seconds later then sends the client hello, and milliseconds after sends a FIN-ACK to the SEIM before getting the ack back the siem.&lt;BR /&gt;&lt;BR /&gt;Why does it wait 106 seconds before sending the client hellp? very strange....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again tls syslog for config and system logs work fine with the same siem.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 21:26:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tls-syslog-to-a-cloud-based-siem/m-p/307621#M79896</guid>
      <dc:creator>ryupapa</dc:creator>
      <dc:date>2020-01-22T21:26:30Z</dc:date>
    </item>
  </channel>
</rss>

