Splunk Enterprise

Intrusion_Detection by IDS_Attacks.signature matching src or soucerype file

Splunk_rocks
Path Finder

Just trying to find way to get src or dst info for matching signature group by values

 

| tstats allow_old_summaries=true count from datamodel=Intrusion_Detection by IDS_Attacks.signature | `drop_dm_object_name("IDS_Attacks")` | search [|inputlookup org_applicationattack.csv| fields signature ] | xswhere count from count_by_signature_1h in ids_attacks by signature is above minimal | where count >50 | fields signature count source ids_type vendor action

Labels (1)
Tags (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The Intrusion_Detection datamodel has both src and dest fields, but your query discards them both.

Verify the src and dest fields have usable data by debugging the query.  Start by stripping it down.

| tstats allow_old_summaries=true count from datamodel=Intrusion_Detection by IDS_Attacks.signature 
| `drop_dm_object_name("IDS_Attacks")` 

If you have usable data at this point, add another command.

| tstats allow_old_summaries=true count from datamodel=Intrusion_Detection by IDS_Attacks.signature 
| `drop_dm_object_name("IDS_Attacks")` 
| search [|inputlookup org_applicationattack.csv| fields signature ] 

Continue this process until the data you needs goes away and you'll have found the cause.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

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