<?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 Prevent events from ingesting in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/506405#M86219</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;after connecting AWS add-on and configuration,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have this query which is filling my index with much unwanted events :&lt;/P&gt;&lt;P&gt;index=cloudtrail "userIdentity.sessionContext.sessionIssuer.userName"=PrismaCloudReadOnlyRole errorCode=success&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;how can I prevent this username from indexing ?&lt;/P&gt;&lt;P&gt;can I do it on the local .conf file ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Sun, 28 Jun 2020 13:32:40 GMT</pubDate>
    <dc:creator>ranmys</dc:creator>
    <dc:date>2020-06-28T13:32:40Z</dc:date>
    <item>
      <title>Prevent events from ingesting</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/506405#M86219</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;after connecting AWS add-on and configuration,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have this query which is filling my index with much unwanted events :&lt;/P&gt;&lt;P&gt;index=cloudtrail "userIdentity.sessionContext.sessionIssuer.userName"=PrismaCloudReadOnlyRole errorCode=success&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;how can I prevent this username from indexing ?&lt;/P&gt;&lt;P&gt;can I do it on the local .conf file ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 28 Jun 2020 13:32:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/506405#M86219</guid>
      <dc:creator>ranmys</dc:creator>
      <dc:date>2020-06-28T13:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent events from ingesting</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/506444#M86224</link>
      <description>&lt;P&gt;Your method to make this work depends on how regular the data is. &amp;nbsp;&lt;SPAN&gt;userIdentity.sessionContext.sessionIssuer.userName sure feels like it comes from JSON. If so, I'd recommend using a sed statement in props.conf on whatever server is first getting hold of parsing phase on the data. &amp;nbsp;For example, on&amp;nbsp;prem either your index or heavy forwarder. &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For example, let's say &lt;/SPAN&gt;&lt;SPAN&gt;your data is pretty regular and looks like this AWS example:&lt;BR /&gt;"userIdentity": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "type": "IAMUser",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "principalId": "AIDAJ45Q7YFFAREXAMPLE",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;"arn": "arn:aws:iam::123456789012:user/Alice",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "accountId": "123456789012",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "accessKeyId": "AKIAIOSFODNN7EXAMPLE",&lt;BR /&gt;&amp;nbsp; &amp;nbsp; "userName": "Alice" }&lt;BR /&gt;&lt;BR /&gt;On the parsing phase you can add a props.conf that uses sed command to&amp;nbsp;strip that username.&lt;BR /&gt;[sourcetype::&amp;lt;whatever&amp;gt;]&lt;BR /&gt;SEDCMD-strip_username = s/accountId":"(\d{12})/accountId":"\1/g&lt;BR /&gt;&lt;BR /&gt;Take that example, and adjust if your data doesn't look like the example.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jun 2020 03:29:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/506444#M86224</guid>
      <dc:creator>The_Simko</dc:creator>
      <dc:date>2020-06-29T03:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent events from ingesting</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/508260#M86490</link>
      <description>&lt;P&gt;You could use props and transforms to filter out data that you dont want and drop into the nullQueue.&lt;/P&gt;&lt;P&gt;Something like this:&lt;/P&gt;&lt;P&gt;props.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[aws:cloudtrail]
TRANSFORMS-0 = ignorePrismaCloudRORole&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;transforms.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ignorePrismaCloudRORole]
REGEX = userIdentity\"\:\s\{\"sessionContext\".+\"sessionIssuer[^\}]+\"userName\": \"ignorePrismaCloudReadOnlyRole\"[^}]+
DEST = queue
FORMAT = nullQueue&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2020 09:20:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Prevent-events-from-ingesting/m-p/508260#M86490</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2020-07-09T09:20:29Z</dc:date>
    </item>
  </channel>
</rss>

