<?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: Using SEDCMD in Splunk Cloud in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349455#M64142</link>
    <description>&lt;P&gt;Your going to need backend access to apply SEDCMD.&lt;/P&gt;

&lt;P&gt;Before doing this, why not just stream PII data to a new restricted index or even better, a restricted environment? &lt;/P&gt;</description>
    <pubDate>Tue, 19 Dec 2017 15:41:27 GMT</pubDate>
    <dc:creator>skoelpin</dc:creator>
    <dc:date>2017-12-19T15:41:27Z</dc:date>
    <item>
      <title>Using SEDCMD in Splunk Cloud</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349454#M64141</link>
      <description>&lt;P&gt;Task: Mask PII data at Index Time&lt;/P&gt;

&lt;P&gt;Current Setup: Universal forwards to forward logs to Splunk&lt;/P&gt;

&lt;P&gt;Based on documentation, SEDCMD seems to be the best option to mask PII data at index time. How can I configure SEDCMD in Splunk Cloud.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2017 14:10:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349454#M64141</guid>
      <dc:creator>catchaj88</dc:creator>
      <dc:date>2017-12-19T14:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: Using SEDCMD in Splunk Cloud</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349455#M64142</link>
      <description>&lt;P&gt;Your going to need backend access to apply SEDCMD.&lt;/P&gt;

&lt;P&gt;Before doing this, why not just stream PII data to a new restricted index or even better, a restricted environment? &lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2017 15:41:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349455#M64142</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2017-12-19T15:41:27Z</dc:date>
    </item>
    <item>
      <title>Re: Using SEDCMD in Splunk Cloud</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349456#M64143</link>
      <description>&lt;P&gt;@skoelpin &lt;/P&gt;

&lt;P&gt;Thanks for the suggestion. We will be definitely using restricted indices for handling PII data. &lt;/P&gt;

&lt;P&gt;However, my objective is to not have any sensitive data available in splunk at all. Do you have any suggestion to achieve that? &lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2017 16:16:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349456#M64143</guid>
      <dc:creator>catchaj88</dc:creator>
      <dc:date>2017-12-19T16:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: Using SEDCMD in Splunk Cloud</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349457#M64144</link>
      <description>&lt;P&gt;Yes, if you want to take the added security then you should apply SEDCMD at index time. This will create a golden copy without the sensitive data. &lt;/P&gt;

&lt;P&gt;This will require an indexer restart &lt;/P&gt;

&lt;P&gt;Place this in your &lt;CODE&gt;props.conf&lt;/CODE&gt; and restart splunkd. You will need to create a regular expression of your PII data and it will replace it with &lt;CODE&gt;XXXXXXXXX&lt;/CODE&gt;. I you need help with the regex, you can post a sample (obviously not the real sample) and I can give you a hand. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype]
 sedcmd-removePII=s/&amp;lt;REGEX OF PII DATA&amp;gt;/XXXXXXXX/g
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I would recommend testing this at search time first to make sure your sedcmd command is working correctly. &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;... | rex mode=sed s/&amp;lt;REGEX OF PII DATA&amp;gt;/XXXXXXXX/g&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2017 18:32:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349457#M64144</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2017-12-19T18:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Using SEDCMD in Splunk Cloud</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349458#M64145</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2017 18:34:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Using-SEDCMD-in-Splunk-Cloud/m-p/349458#M64145</guid>
      <dc:creator>catchaj88</dc:creator>
      <dc:date>2017-12-19T18:34:21Z</dc:date>
    </item>
  </channel>
</rss>

