<?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 How to implement data diode-like forwarding between two distinct Splunk instances? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-implement-data-diode-like-forwarding-between-two-distinct/m-p/173196#M34833</link>
    <description>&lt;P&gt;Our customer would like to deploy two Splunk instances. The first instance would be in an open network and the another one would be in a highly protected network. No data is allowed to leave the protected network. From the open network, some data flow (on UDP protocol) is allowed to reach the protected network.&lt;BR /&gt;
The customer would like to forward some interesting events from a Splunk indexer found in the open network to another Splunk indexer found in the protected network. So they would like to implement a data diode-like (unidirectional network) behaviour.&lt;/P&gt;

&lt;P&gt;What is the best and safe way to achieve this?&lt;/P&gt;</description>
    <pubDate>Thu, 13 Aug 2015 15:15:28 GMT</pubDate>
    <dc:creator>ngiczi</dc:creator>
    <dc:date>2015-08-13T15:15:28Z</dc:date>
    <item>
      <title>How to implement data diode-like forwarding between two distinct Splunk instances?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-implement-data-diode-like-forwarding-between-two-distinct/m-p/173196#M34833</link>
      <description>&lt;P&gt;Our customer would like to deploy two Splunk instances. The first instance would be in an open network and the another one would be in a highly protected network. No data is allowed to leave the protected network. From the open network, some data flow (on UDP protocol) is allowed to reach the protected network.&lt;BR /&gt;
The customer would like to forward some interesting events from a Splunk indexer found in the open network to another Splunk indexer found in the protected network. So they would like to implement a data diode-like (unidirectional network) behaviour.&lt;/P&gt;

&lt;P&gt;What is the best and safe way to achieve this?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Aug 2015 15:15:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-implement-data-diode-like-forwarding-between-two-distinct/m-p/173196#M34833</guid>
      <dc:creator>ngiczi</dc:creator>
      <dc:date>2015-08-13T15:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement data diode-like forwarding between two distinct Splunk instances?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-implement-data-diode-like-forwarding-between-two-distinct/m-p/173197#M34834</link>
      <description>&lt;P&gt;Take a look &lt;A href="http://answers.splunk.com/answers/203547/index-and-forward-data-into-another-splunk-instanc.html"&gt;here&lt;/A&gt; for the general approach on how to index and forward. The only issue here is if UDP is your only protocol choice, that will not work since the Splunk-2-Splunk link will require TCP.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Aug 2015 20:07:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-implement-data-diode-like-forwarding-between-two-distinct/m-p/173197#M34834</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2015-08-13T20:07:40Z</dc:date>
    </item>
  </channel>
</rss>

