Getting Data In

Prevent events from ingesting

ranmys
Loves-to-Learn

Hello,

after connecting AWS add-on and configuration, 

I have this query which is filling my index with much unwanted events :

index=cloudtrail "userIdentity.sessionContext.sessionIssuer.userName"=PrismaCloudReadOnlyRole errorCode=success

 

how can I prevent this username from indexing ?

can I do it on the local .conf file ?

Thanks

Labels (2)
Tags (2)
0 Karma

livehybrid
SplunkTrust
SplunkTrust

You could use props and transforms to filter out data that you dont want and drop into the nullQueue.

Something like this:

props.conf

 

[aws:cloudtrail]
TRANSFORMS-0 = ignorePrismaCloudRORole

 

transforms.conf

 

[ignorePrismaCloudRORole]
REGEX = userIdentity\"\:\s\{\"sessionContext\".+\"sessionIssuer[^\}]+\"userName\": \"ignorePrismaCloudReadOnlyRole\"[^}]+
DEST = queue
FORMAT = nullQueue

 

0 Karma

The_Simko
Path Finder

Your method to make this work depends on how regular the data is.  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.  For example, on prem either your index or heavy forwarder.  

For example, let's say
your data is pretty regular and looks like this AWS example:
"userIdentity": {
    "type": "IAMUser",
    "principalId": "AIDAJ45Q7YFFAREXAMPLE",
     "arn": "arn:aws:iam::123456789012:user/Alice",
    "accountId": "123456789012",
    "accessKeyId": "AKIAIOSFODNN7EXAMPLE",
    "userName": "Alice" }

On the parsing phase you can add a props.conf that uses sed command to strip that username.
[sourcetype::<whatever>]
SEDCMD-strip_username = s/accountId":"(\d{12})/accountId":"\1/g

Take that example, and adjust if your data doesn't look like the example.


0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...