<?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 Best practices for Splunking mobile endpoints in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Best-practices-for-Splunking-mobile-endpoints/m-p/399454#M71161</link>
    <description>&lt;P&gt;I'd just like to hear from anyone who has implemented a successful strategy for Splunking mobile endpoints (Windows, OSX, Linux...).&lt;/P&gt;
&lt;P&gt;It would seem to me that since accelerated data models run every five minutes by default, capturing events from mobile endpoints would need to happen in &amp;lt;5 min window. So, having a Universal Forwarder that can only forward data when on a VPN, or physically connected to the corporate network seems like a losing strategy.&lt;/P&gt;
&lt;P&gt;This would mean having some kind of intermediate forwarder and deployment server available to the Internet.&lt;/P&gt;
&lt;P&gt;Has anyone tried this?&lt;BR /&gt;&lt;BR /&gt;What kind of security controls and tools did you use to protect the Internet-facing Splunk infrastructure?&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;C&lt;/P&gt;</description>
    <pubDate>Sat, 06 Jun 2020 23:58:21 GMT</pubDate>
    <dc:creator>responsys_cm</dc:creator>
    <dc:date>2020-06-06T23:58:21Z</dc:date>
    <item>
      <title>Best practices for Splunking mobile endpoints</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practices-for-Splunking-mobile-endpoints/m-p/399454#M71161</link>
      <description>&lt;P&gt;I'd just like to hear from anyone who has implemented a successful strategy for Splunking mobile endpoints (Windows, OSX, Linux...).&lt;/P&gt;
&lt;P&gt;It would seem to me that since accelerated data models run every five minutes by default, capturing events from mobile endpoints would need to happen in &amp;lt;5 min window. So, having a Universal Forwarder that can only forward data when on a VPN, or physically connected to the corporate network seems like a losing strategy.&lt;/P&gt;
&lt;P&gt;This would mean having some kind of intermediate forwarder and deployment server available to the Internet.&lt;/P&gt;
&lt;P&gt;Has anyone tried this?&lt;BR /&gt;&lt;BR /&gt;What kind of security controls and tools did you use to protect the Internet-facing Splunk infrastructure?&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;C&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jun 2020 23:58:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practices-for-Splunking-mobile-endpoints/m-p/399454#M71161</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2020-06-06T23:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for Splunking mobile endpoints</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Best-practices-for-Splunking-mobile-endpoints/m-p/399455#M71162</link>
      <description>&lt;P&gt;Good question. I would be interested how this is done for off network systems.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 16:49:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Best-practices-for-Splunking-mobile-endpoints/m-p/399455#M71162</guid>
      <dc:creator>TheSplunkDude</dc:creator>
      <dc:date>2020-06-03T16:49:06Z</dc:date>
    </item>
  </channel>
</rss>

