<?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/SSL Syslog Splunk Support in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TLS-SSL-Syslog-Splunk-Support/m-p/60432#M11983</link>
    <description>&lt;P&gt;Splunk does support a TCP w/ SSL input.  See &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf&lt;/A&gt; .  I have no experience to say how well this works with an rsyslog SSL sender.&lt;/P&gt;

&lt;P&gt;It does, not, however, support syslog via UDP and DTLS.  But, I don't think rsyslog can do this either (I may be wrong there).&lt;/P&gt;

&lt;P&gt;Best practice (and my personal preference) is to still install a forwarder.  It can definitely do SSL to Splunk, and can also support scripted inputs and other non-syslog data coming from those machines.&lt;/P&gt;</description>
    <pubDate>Fri, 25 May 2012 17:38:10 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2012-05-25T17:38:10Z</dc:date>
    <item>
      <title>TLS/SSL Syslog Splunk Support</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TLS-SSL-Syslog-Splunk-Support/m-p/60431#M11982</link>
      <description>&lt;P&gt;I'm always nervous about sending plain text syslogs around the place, and rsyslog has some fantastic options (SSL and TLS). &lt;/P&gt;

&lt;P&gt;Does splunk support reading these connectors, or would I have to setup a client / forwarder setup on the local box to do this? &lt;/P&gt;

&lt;P&gt;I am not talking about a secured tunnel here. &lt;/P&gt;</description>
      <pubDate>Fri, 25 May 2012 10:21:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TLS-SSL-Syslog-Splunk-Support/m-p/60431#M11982</guid>
      <dc:creator>pacepace</dc:creator>
      <dc:date>2012-05-25T10:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: TLS/SSL Syslog Splunk Support</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TLS-SSL-Syslog-Splunk-Support/m-p/60432#M11983</link>
      <description>&lt;P&gt;Splunk does support a TCP w/ SSL input.  See &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf&lt;/A&gt; .  I have no experience to say how well this works with an rsyslog SSL sender.&lt;/P&gt;

&lt;P&gt;It does, not, however, support syslog via UDP and DTLS.  But, I don't think rsyslog can do this either (I may be wrong there).&lt;/P&gt;

&lt;P&gt;Best practice (and my personal preference) is to still install a forwarder.  It can definitely do SSL to Splunk, and can also support scripted inputs and other non-syslog data coming from those machines.&lt;/P&gt;</description>
      <pubDate>Fri, 25 May 2012 17:38:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TLS-SSL-Syslog-Splunk-Support/m-p/60432#M11983</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-05-25T17:38:10Z</dc:date>
    </item>
  </channel>
</rss>

