Getting Data In

How to narrow Scope of WinNetMon Input to Domain Users?

cfloquet
Path Finder

Hello, 

Thank you for taking the time to consider my question, I'm currently configuring an custom app to deploy to Windows workstations to monitor both inbound and outbound connections strictly for domain users, to correlate the foreign IPv4s with phishing/C2 addresses we obtain via threat intelligence. 

To avoid the noise made by local or system level accounts, I would like to specify the "user" field within appName/local/inputs.conf using regex, as outlined in Splunk inputs.conf documentation, unfortunately there is no clear example of how regex can be used to do a simple restriction to only domain level accounts, which is a very common use case I'd imagine. 

What I would like to accomplish is a version of the following:

[WinNetMon://inbound-mon]

disabled=0

<...>

user=domain\*

This would effectively only monitor the inbound connections made by users that are preceded with the company domain, and thus eliminate traffic/noise from the endpoint gathering updates etc. 

Please advise on the best way to accomplish this, any working answer will be happily greeted with karma and accepted as the final solution, many thanks in advance!

 

 

Labels (3)
0 Karma
1 Solution

cfloquet
Path Finder

"Fine, I'll do it myself..."

[WinNetMon://<name of monitor input>]

disabled=0

<...>

user=domain\\(.*)

I have tested this and it works as expected, at least for me it did. 

View solution in original post

0 Karma

cfloquet
Path Finder

"Fine, I'll do it myself..."

[WinNetMon://<name of monitor input>]

disabled=0

<...>

user=domain\\(.*)

I have tested this and it works as expected, at least for me it did. 

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!

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