Getting Data In

Login Activity

itsmevic
Communicator

I need to check the logs against Workstation XYZ to ensure no one else besides JDOE has logged into it from 9/15/20 00:00:00.000  until 9/22/20. 23:59;59.999 (7-days).  What would be the best SPL to run to check this? 

Labels (1)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi @itsmevic,

if you're speking of windows logs, you should try something like this:

index=wineventlog EventCode=4624 workstation=XYZ user!=JDOE

please check if the fields workstation and user are written in your logs in this way, because I have an italian Windows and I have different fieldnames, but anyway you can see the approach.

Ciao.

Giuseppe

View solution in original post

itsmevic
Communicator

Thank you both! 

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @itsmevic,

if you're speking of windows logs, you should try something like this:

index=wineventlog EventCode=4624 workstation=XYZ user!=JDOE

please check if the fields workstation and user are written in your logs in this way, because I have an italian Windows and I have different fieldnames, but anyway you can see the approach.

Ciao.

Giuseppe

ITWhisperer
SplunkTrust
SplunkTrust

Search for login events where workstation = XYZ where user != JDOE

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

Analytics Workspace removal in Splunk 10.6

In Splunk Cloud Platform and Splunk Enterprise 10.6, Analytics Workspace is removed from product and no longer ...

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...