<?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 Scanning Splunk data for secret leaking? in Security</title>
    <link>https://community.splunk.com/t5/Security/Scanning-Splunk-data-for-secret-leaking/m-p/633530#M16613</link>
    <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;We know that there are several options to mask sensitive data before/during ingestion. But generally, how do you scan your data to check if there is any already existing leakage of secrets/tokens/password? I've googled and searched community, but I did not find anything. I thought there is a Splunk app or Splunk ES has a built-in feature to do this, like a professional, fast, effective alert or an AI/ML assisted one.&lt;/P&gt;&lt;P&gt;What I've done so far for a few indexes:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index={INDEXNAME}  | stats  values(*) AS *   | transpose  | table  column   | rename  column AS Fieldnames  | search Fieldnames=*secret* OR Fieldnames=*password*&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(with last 15 minutes search interval)&lt;/P&gt;&lt;P&gt;Is there any better solution out? Or do you have better idea to handle this? How are others doing this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a Splunk Cloud Platform, but I think it would be the same for Enterprise as well.&lt;/P&gt;&lt;P&gt;Thank you very much!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;DG&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Mar 2023 08:46:57 GMT</pubDate>
    <dc:creator>DG</dc:creator>
    <dc:date>2023-03-07T08:46:57Z</dc:date>
    <item>
      <title>Scanning Splunk data for secret leaking?</title>
      <link>https://community.splunk.com/t5/Security/Scanning-Splunk-data-for-secret-leaking/m-p/633530#M16613</link>
      <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;We know that there are several options to mask sensitive data before/during ingestion. But generally, how do you scan your data to check if there is any already existing leakage of secrets/tokens/password? I've googled and searched community, but I did not find anything. I thought there is a Splunk app or Splunk ES has a built-in feature to do this, like a professional, fast, effective alert or an AI/ML assisted one.&lt;/P&gt;&lt;P&gt;What I've done so far for a few indexes:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index={INDEXNAME}  | stats  values(*) AS *   | transpose  | table  column   | rename  column AS Fieldnames  | search Fieldnames=*secret* OR Fieldnames=*password*&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(with last 15 minutes search interval)&lt;/P&gt;&lt;P&gt;Is there any better solution out? Or do you have better idea to handle this? How are others doing this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a Splunk Cloud Platform, but I think it would be the same for Enterprise as well.&lt;/P&gt;&lt;P&gt;Thank you very much!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;DG&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2023 08:46:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Scanning-Splunk-data-for-secret-leaking/m-p/633530#M16613</guid>
      <dc:creator>DG</dc:creator>
      <dc:date>2023-03-07T08:46:57Z</dc:date>
    </item>
  </channel>
</rss>

