Splunk Search

How to exclude notable events from triggering using erex?

mdicenzo
Explorer

We have notable events for when a user is created on multiple devices. Most of them are expected for when devices are imaged. 

I want to use erex to create a suppression for like accounts. They typically have the same beginning and are followed by 2 numbers. Example would ituser23, ituser24, ituser25. 

I am using the search below for testing

index=notable source="Endpoint - Anomalous User Account Creation - Rule" | erex user examples="ituser23, ituser24, ituser25" 

I am still getting user accounts that are unrelated such as phone or tablet.

When I look at the recommended regex it seems like it is not being granular enough.

Labels (1)
Tags (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Skip erex and go directly to the regex command.  This query will filter out users with names consisting of "ituser" followed by 2 digits.

index=notable source="Endpoint - Anomalous User Account Creation - Rule" 
| regex user!="^ituser\d\d$"

 

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Skip erex and go directly to the regex command.  This query will filter out users with names consisting of "ituser" followed by 2 digits.

index=notable source="Endpoint - Anomalous User Account Creation - Rule" 
| regex user!="^ituser\d\d$"

 

---
If this reply helps you, Karma would be appreciated.

mdicenzo
Explorer

This is eventually how I did this. Thank you for the help!

0 Karma

richgalloway
SplunkTrust
SplunkTrust

If your problem is resolved, then please click the "Accept as Solution" button to help future readers.

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

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...