<?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 Mask sensitive data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Mask-sensitive-data/m-p/434812#M95067</link>
    <description>&lt;P&gt;Hi everyone! we are trying to anonymize sensitive information using SEDCMD on props.conf file in the local folder but we haven't gotten success due to a weird behavior, for exemple when we have a simple log &lt;BR /&gt;
we can easily mask it but a complex one we can not &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;SEDCMD = s/Senha:[0-9a-zA-Z]{0,32}/Senha:****/g&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Bellow follows the log that we consider complex: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{"Bola":"2019-06-17T22:08:26.400-03:00","pato":"Arquitetura","application":"PineOnline","tatu":"ResetarSenha","result":"false", 
"reqId":"6276A957-0E26-439E-8418-EB7BBBA618A8","version":"","platform":"","httpStatus":"200","reasonCode":"200","url":"https://888282121:999/Path1/Path2", 
"metodo":"PUT","tempo":"37","userAgent":"","request": {"ip":"","host":"192.168.0.103","client":"ClientIp:888.88.0.888","application-key":"","authorization":"", 
"customer-hash":"PZyKLE+0ONEfqlZyLgFe7owpccZl3iCdbYqSHiqGY_78y5PSOu+5MKh_MXk84EWKh0Cl5LHXzz+nUEEMPQCOirT5Hu01PvFAerq4ncoYszS8ZIYRpvg8P+zJMfWhT0KrcNXgDPliDXLFuK_gSIydc4QCDiY4MKXRNWn2ygpiiaEletMqkRh2wFALq7Bc5E0iMItlB6jO4mPduR95u+FCPvGn5ynrdtCzjRMciRH1IaL1vtRQijOFUsurwy_L_fGP0g5BUUohPYbBKFTjkFFTiAR11s9jQD2wZ3_pUjmIRgePfkdH021k9RsQrQQ+dr0c23EyEeLd9P+HURJg==",
"payload": [{"CPF":"7878787878",Senha:58586762}]},"response": {"host":"192.168.0.20","payload": []}} 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In our test we realized that when we use a very large payload the transformation does not occur, when we use smaller payload everything seems to work. &lt;/P&gt;

&lt;P&gt;Reference: &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/Anonymizedata#Anonymize_data_through_a_sed_script"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/Anonymizedata#Anonymize_data_through_a_sed_script&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jun 2019 15:02:04 GMT</pubDate>
    <dc:creator>justodaniel</dc:creator>
    <dc:date>2019-06-19T15:02:04Z</dc:date>
    <item>
      <title>Mask sensitive data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Mask-sensitive-data/m-p/434812#M95067</link>
      <description>&lt;P&gt;Hi everyone! we are trying to anonymize sensitive information using SEDCMD on props.conf file in the local folder but we haven't gotten success due to a weird behavior, for exemple when we have a simple log &lt;BR /&gt;
we can easily mask it but a complex one we can not &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;SEDCMD = s/Senha:[0-9a-zA-Z]{0,32}/Senha:****/g&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Bellow follows the log that we consider complex: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{"Bola":"2019-06-17T22:08:26.400-03:00","pato":"Arquitetura","application":"PineOnline","tatu":"ResetarSenha","result":"false", 
"reqId":"6276A957-0E26-439E-8418-EB7BBBA618A8","version":"","platform":"","httpStatus":"200","reasonCode":"200","url":"https://888282121:999/Path1/Path2", 
"metodo":"PUT","tempo":"37","userAgent":"","request": {"ip":"","host":"192.168.0.103","client":"ClientIp:888.88.0.888","application-key":"","authorization":"", 
"customer-hash":"PZyKLE+0ONEfqlZyLgFe7owpccZl3iCdbYqSHiqGY_78y5PSOu+5MKh_MXk84EWKh0Cl5LHXzz+nUEEMPQCOirT5Hu01PvFAerq4ncoYszS8ZIYRpvg8P+zJMfWhT0KrcNXgDPliDXLFuK_gSIydc4QCDiY4MKXRNWn2ygpiiaEletMqkRh2wFALq7Bc5E0iMItlB6jO4mPduR95u+FCPvGn5ynrdtCzjRMciRH1IaL1vtRQijOFUsurwy_L_fGP0g5BUUohPYbBKFTjkFFTiAR11s9jQD2wZ3_pUjmIRgePfkdH021k9RsQrQQ+dr0c23EyEeLd9P+HURJg==",
"payload": [{"CPF":"7878787878",Senha:58586762}]},"response": {"host":"192.168.0.20","payload": []}} 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In our test we realized that when we use a very large payload the transformation does not occur, when we use smaller payload everything seems to work. &lt;/P&gt;

&lt;P&gt;Reference: &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/Anonymizedata#Anonymize_data_through_a_sed_script"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/Anonymizedata#Anonymize_data_through_a_sed_script&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2019 15:02:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Mask-sensitive-data/m-p/434812#M95067</guid>
      <dc:creator>justodaniel</dc:creator>
      <dc:date>2019-06-19T15:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: Mask sensitive data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Mask-sensitive-data/m-p/434813#M95068</link>
      <description>&lt;P&gt;Strange. When I upload that specific sample event into splunk and set that exact SEDCMD, it works just fine.&lt;/P&gt;

&lt;P&gt;Can you perhaps share some more info on your setup and how and where you have set this configuration? Is it just for a single sourcetype, or are you using this for several sourcetypes and is one of those working and another not?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2019 15:12:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Mask-sensitive-data/m-p/434813#M95068</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2019-06-19T15:12:39Z</dc:date>
    </item>
  </channel>
</rss>

