<?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: Unmask fields on adhoc basis in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-unmask-fields-on-adhoc-basis/m-p/633038#M108388</link>
    <description>&lt;P&gt;If you're masking the data using SEDCMD or a transform then there's no "unmasking".&amp;nbsp; The original data has been replaced and cannot be recovered.&lt;/P&gt;&lt;P&gt;A workaround would be to clone the data to a separate index with limited read access.&amp;nbsp; Then you'd have to pull the unmasked data from the new index in addition to the masked data from the current index.&lt;/P&gt;&lt;P&gt;Perhaps you can use Ingest Actions to only mask non-abc data.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Mar 2023 16:40:39 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-03-02T16:40:39Z</dc:date>
    <item>
      <title>How to unmask fields on adhoc basis?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-unmask-fields-on-adhoc-basis/m-p/633023#M108386</link>
      <description>&lt;P&gt;Hi All ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a sensitive field that we mask regularly ,but a use case has come where we have to store the particular filed as it is (without masking) based on a&amp;nbsp; field value .does anyone have faced any case like that before ?&lt;/P&gt;
&lt;P&gt;current scenario&amp;nbsp;&lt;/P&gt;
&lt;P&gt;customer_data ==xxxx&amp;nbsp; specific_filed=abc&lt;/P&gt;
&lt;P&gt;customer_data ==xxxx&amp;nbsp; specific_filed=def&lt;/P&gt;
&lt;P&gt;customer_data ==xxxx&amp;nbsp; specific_filed=ghi&lt;/P&gt;
&lt;P&gt;expected output&amp;nbsp;&lt;/P&gt;
&lt;P&gt;based on an adhoc request we have to unmask now the incoming data for field abc&lt;/P&gt;
&lt;P&gt;customer_data ==12345 specific_filed=abc&lt;/P&gt;
&lt;P&gt;customer_data ==xxxx&amp;nbsp; specific_filed=def&lt;/P&gt;
&lt;P&gt;customer_data ==xxxx&amp;nbsp; specific_filed=ghi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 17:16:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-unmask-fields-on-adhoc-basis/m-p/633023#M108386</guid>
      <dc:creator>Chiranjeev88</dc:creator>
      <dc:date>2023-03-02T17:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: Unmask fields on adhoc basis</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-unmask-fields-on-adhoc-basis/m-p/633038#M108388</link>
      <description>&lt;P&gt;If you're masking the data using SEDCMD or a transform then there's no "unmasking".&amp;nbsp; The original data has been replaced and cannot be recovered.&lt;/P&gt;&lt;P&gt;A workaround would be to clone the data to a separate index with limited read access.&amp;nbsp; Then you'd have to pull the unmasked data from the new index in addition to the masked data from the current index.&lt;/P&gt;&lt;P&gt;Perhaps you can use Ingest Actions to only mask non-abc data.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Mar 2023 16:40:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-unmask-fields-on-adhoc-basis/m-p/633038#M108388</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-03-02T16:40:39Z</dc:date>
    </item>
  </channel>
</rss>

