Splunk Search

Check connection from same source to multiple destination

SIEMStudent
Path Finder

Hi guys,

I have a doubt regarding the mapping of connection from the same source IP to different destination IP.

In my query, I have to check if the same source reach more than 300 different destination IP.

Usually, If I had to report connection with source ip which appear more than 300 times, I know I can to write:

 

|stats count src_ip as source by source
|where count > 300 

 

But what about if I have to check the query requirements?

It shuold be something like:

|stats count src_ip as source, dest_ip as destination by source
|where destination > 300 

?

Labels (2)
0 Karma
1 Solution

scelikok
SplunkTrust
SplunkTrust

Hi @SIEMStudent,

You can try below;

| stats dc(dest_ip) as dest_count by src_ip
| where dest_count > 300 
If this reply helps you an upvote and "Accept as Solution" is appreciated.

View solution in original post

scelikok
SplunkTrust
SplunkTrust

Hi @SIEMStudent,

You can try below;

| stats dc(dest_ip) as dest_count by src_ip
| where dest_count > 300 
If this reply helps you an upvote and "Accept as Solution" is appreciated.

SIEMStudent
Path Finder

Thank you very much!

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!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...