<?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: Anonymizing (Masking) Data Using SEDCMD in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699622#M20290</link>
    <description>&lt;P&gt;Yes..... Is there a way to implement masking globally?&amp;nbsp; If not, I assume we to add each sourcetype in props.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Sep 2024 17:58:17 GMT</pubDate>
    <dc:creator>computermathguy</dc:creator>
    <dc:date>2024-09-19T17:58:17Z</dc:date>
    <item>
      <title>Anonymizing (Masking) Data Using SEDCMD</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699446#M20280</link>
      <description>&lt;P&gt;As a test, I first created some credit card numbers using a python script.&lt;/P&gt;
&lt;P&gt;I placed the script, along with inputs and props, on the search head. I only placed props on the indexers.&lt;/P&gt;
&lt;P&gt;The following SEDCMD will&amp;nbsp; mask the 1st and 3rd set of 4-digits. The two groups (2nd and 4th set of 4-digits) will not be masked.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;props:
[cc_generator]
SEDCMD-maskcc = s/\d{4}-(\d{4})-\d{4}-(\d{4})/xxxx-\1-xxxx-\2/g 

inputs:
[script://./bin/my_cc_generator.py]
interval = */30 * * * *
sourcetype = cc_generator
disabled = 0
index = mypython

output:
xxxx-9874-xxxx-9484&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 18 Sep 2024 19:07:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699446#M20280</guid>
      <dc:creator>computermathguy</dc:creator>
      <dc:date>2024-09-18T19:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: Anonymizing (Masking) Data Using SEDCMD</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699451#M20281</link>
      <description>&lt;P&gt;Is there a question here?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 18:02:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699451#M20281</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2024-09-18T18:02:26Z</dc:date>
    </item>
    <item>
      <title>Re: Anonymizing (Masking) Data Using SEDCMD</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699622#M20290</link>
      <description>&lt;P&gt;Yes..... Is there a way to implement masking globally?&amp;nbsp; If not, I assume we to add each sourcetype in props.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 17:58:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699622#M20290</guid>
      <dc:creator>computermathguy</dc:creator>
      <dc:date>2024-09-19T17:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: Anonymizing (Masking) Data Using SEDCMD</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699630#M20291</link>
      <description>&lt;P&gt;You could attach your props to some wildcarded host or source stanza but that's something I'd be very careful about. It's a very non-obvious configuration and can be a huge pain to debug issues.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 18:26:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Anonymizing-Masking-Data-Using-SEDCMD/m-p/699630#M20291</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-09-19T18:26:41Z</dc:date>
    </item>
  </channel>
</rss>

