Getting Data In

Capturing AD Authenticated Applications

heats
Explorer

Scenario: We're doing an active directory upgrade which will effect applications that currently point to specific domain controller for authentication.

We have so many applications in use right now and some stem back to before when most of us were employed. I'm wondering if there's any way to construct something within Splunk that would be able to track applications that are authenticating via. active directory. Would it just give the servers the apps are housed on or is there a way to get specific information relating to the application itself?

I believe my first step is to get Splunk on the domain controllers, after that I'm unsure and I just wanted to see if this was something anyone on here has ever dealt with or had experience with.

As always thanks to anyone who takes the time out to read this and even more thanks if anyone has suggestions!

0 Karma

sselvaraj_splun
Splunk Employee
Splunk Employee

Hope it is possible to derive the data as requested.

Scenario: If you are collecting logs from the domain controller(DC) by using Splunk.
In general, On every single authentication task performed by any domain user, a respective Windows security event log generated.
On that case, If you search for the event ID in the 4624 and from the "Process Information" or "Process Name" column you can get the application name which got authorization from DC.

Splunk search command : host="DC1" EventCode=4624 Process_Name=*

Reference: https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventID=4624#examples

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