<?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: mask anonymize data by role in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37461#M6912</link>
    <description>&lt;P&gt;Splunk doesn't have a mechanism to anonymize data at search time - it can only anonymize it at index-time. &lt;/P&gt;

&lt;P&gt;To protect indexed sensitive data, you would need to filter it based on role to prevent access.&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2019 14:31:28 GMT</pubDate>
    <dc:creator>qodeninja</dc:creator>
    <dc:date>2019-07-31T14:31:28Z</dc:date>
    <item>
      <title>mask anonymize data by role</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37456#M6907</link>
      <description>&lt;P&gt;Is there a way to mask or anonymize data  in splunk by role such that one role (such as Admin) can see all the data on splunk however another role (such as user1)can only see the masked or anonymized data. &lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2011 21:54:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37456#M6907</guid>
      <dc:creator>amitosr</dc:creator>
      <dc:date>2011-12-19T21:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: mask anonymize data by role</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37457#M6908</link>
      <description>&lt;P&gt;Wow i thought i could have it answered here, i will update once i get a solution to this :). Waiting on a response from Splunk support.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Dec 2011 23:08:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37457#M6908</guid>
      <dc:creator>amitosr</dc:creator>
      <dc:date>2011-12-20T23:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: mask anonymize data by role</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37458#M6909</link>
      <description>&lt;P&gt;No solution yet.!!&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2012 22:22:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37458#M6909</guid>
      <dc:creator>amitosr</dc:creator>
      <dc:date>2012-01-09T22:22:02Z</dc:date>
    </item>
    <item>
      <title>Re: mask anonymize data by role</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37459#M6910</link>
      <description>&lt;P&gt;I don't know of a way to do this with Splunk's role based permissions on objects or at search time.&lt;/P&gt;

&lt;P&gt;A potential solution/hack , albeit not very "license volume efficent", might be to index the data twice.&lt;BR /&gt;
Index A indexes the data in plaintext , Index B indexes the same data but anonymized. &lt;/P&gt;

&lt;P&gt;And then make Index A only readable to those in the &lt;STRONG&gt;&lt;EM&gt;admin&lt;/EM&gt;&lt;/STRONG&gt; role and Index B readable to those in the &lt;STRONG&gt;&lt;EM&gt;user1&lt;/EM&gt;&lt;/STRONG&gt; role.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2012 23:34:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37459#M6910</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2012-01-09T23:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: mask anonymize data by role</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37460#M6911</link>
      <description>&lt;P&gt;Yes this is what I would suggest, as well. I'd use saved searches to pipe the search results through a custom command that scrubs the fields out of the data and writes a copy of every record into another index. Since this would not be running through any of the inputs it would not count against licensing volume (as with summary indexing), but would require additional disk.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2012 23:58:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37460#M6911</guid>
      <dc:creator>gcoles</dc:creator>
      <dc:date>2012-01-09T23:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: mask anonymize data by role</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37461#M6912</link>
      <description>&lt;P&gt;Splunk doesn't have a mechanism to anonymize data at search time - it can only anonymize it at index-time. &lt;/P&gt;

&lt;P&gt;To protect indexed sensitive data, you would need to filter it based on role to prevent access.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 14:31:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/mask-anonymize-data-by-role/m-p/37461#M6912</guid>
      <dc:creator>qodeninja</dc:creator>
      <dc:date>2019-07-31T14:31:28Z</dc:date>
    </item>
  </channel>
</rss>

