<?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: Recommendations on how best to ingest SECURE TCP (Encrypted Syslog) with AirWatch in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/604024#M105064</link>
    <description>&lt;P&gt;I suppose you could try to fiddle with tcp input and configuring tls settings for it - should be possible but not very convenient.&lt;/P&gt;&lt;P&gt;You can also do it with rsyslog. Configure imtcp - not imptcp - input and either write to files for UF to read or send directly to HEC input on Splunk.&lt;/P&gt;&lt;P&gt;You probably can do similar thing with sc4s but I'm not an expert here.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jun 2022 18:47:23 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2022-06-30T18:47:23Z</dc:date>
    <item>
      <title>How best to ingest SECURE TCP (Encrypted Syslog) with AirWatch?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/603981#M105059</link>
      <description>&lt;P&gt;Are there any recommendations on how best to ingest TLS encrypted syslog from AirWatch Cloud Console?&amp;nbsp; The only settings in AirWatch are to select UDP, TCP or SECURETCP and the port.&amp;nbsp; I opened a case with VMWare and they suggested to open a case with our SIEM provider for recommedations.&amp;nbsp; I suspect the recommendation may be to send logs to an rsyslog and then use forwarder to send to splunk since that supports SSL to Splunk.&amp;nbsp; Has anyone successfully done Encrypted Syslog from Airwatch?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 21:18:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/603981#M105059</guid>
      <dc:creator>banjo5</dc:creator>
      <dc:date>2022-06-30T21:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Recommendations on how best to ingest SECURE TCP (Encrypted Syslog) with AirWatch</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/604009#M105062</link>
      <description>&lt;P&gt;I'm running into the same issue, but with Ricoh printers.&amp;nbsp; But my direction will be what you outlined with sending to SYSLOG, writing to file and forwarder to read that file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 18:04:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/604009#M105062</guid>
      <dc:creator>dokaas_2</dc:creator>
      <dc:date>2022-06-30T18:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: Recommendations on how best to ingest SECURE TCP (Encrypted Syslog) with AirWatch</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/604024#M105064</link>
      <description>&lt;P&gt;I suppose you could try to fiddle with tcp input and configuring tls settings for it - should be possible but not very convenient.&lt;/P&gt;&lt;P&gt;You can also do it with rsyslog. Configure imtcp - not imptcp - input and either write to files for UF to read or send directly to HEC input on Splunk.&lt;/P&gt;&lt;P&gt;You probably can do similar thing with sc4s but I'm not an expert here.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 18:47:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-best-to-ingest-SECURE-TCP-Encrypted-Syslog-with-AirWatch/m-p/604024#M105064</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-06-30T18:47:23Z</dc:date>
    </item>
  </channel>
</rss>

