Installation

Domain Controller computer logons?

wilcompl1334
Explorer

I'm currently dealing with an environment with a number of domain controllers that will need to begin forwarding Windows event logs into Splunk. A worry is license threshold.

I've whitelisted only the event codes we are interested in, but this has done little as 4624/4634, account logons/logoffs, have a lot of noise with network logons. I've toyed with blacklisting any logon using a computer's sAMAccountName$. This drops off our license usage per DC immensely, but I'm worried that we might be missing some valuable event data.

Does anyone have any insight to if this is a good/bad practice, what types of info we'd be missing out on, and/or any alternative suggestions to minimizing the load that DC's place on license usage?

Labels (2)
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...