Splunk Enterprise Security

In Splunk Enterprise Security, can you help me fix my search that uses the tstats command with a NOT operator?

jvanbibber
New Member

I'm trying to use the NOT operator in a search to exclude internal destination traffic. Any help would be great!

| tstats summariesonly=t count from datamodel=Network_Traffic where * by All_Traffic.dest All_Traffic.src | sort - count
0 Karma
1 Solution

pkeenan87
Communicator

You could try and exclude RFC 1918 ranges from the dest field

| tstats summariesonly=t count from datamodel=Network_Traffic where All_Traffic.dest!=10.0.0.0/8 AND All_Traffic.dest!=172.16.0.0/12 AND All_Traffic.dest!=192.168.0.0/16 by All_Traffic.dest All_Traffic.src | sort - count

View solution in original post

0 Karma

pkeenan87
Communicator

You could try and exclude RFC 1918 ranges from the dest field

| tstats summariesonly=t count from datamodel=Network_Traffic where All_Traffic.dest!=10.0.0.0/8 AND All_Traffic.dest!=172.16.0.0/12 AND All_Traffic.dest!=192.168.0.0/16 by All_Traffic.dest All_Traffic.src | sort - count
0 Karma

jvanbibber
New Member

Will give it a try, thank you!

0 Karma

FrankVl
Ultra Champion

And how would you recognize internal destination traffic in your case? Do you have asset enrichments in place, so you can do All_Traffic.dest_category!=internal or so?

Hard to help with this little information. We'll need better info on what your data looks like, how you think you want to recognize internal destinations and what you have tried so far.

0 Karma

jvanbibber
New Member

Well, based on IP private IP ranges is a good place to start, don't you think? 10.0.0.0/8
I don't know how I would incorporate that into the search string

0 Karma
Get Updates on the Splunk Community!

Splunk Search APIを使えば調査過程が残せます

   このゲストブログは、JCOM株式会社の情報セキュリティ本部・専任部長である渡辺慎太郎氏によって執筆されました。 Note: This article is published in both Japanese ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...