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.
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...