azureblog.co.uk
← cd ~/events
// events/4624 · Sign-in

Event ID 4624An account was successfully logged on

A logon session was created on the computer that was accessed. The Logon Type field tells you how (2 interactive, 3 network, 4 batch, 5 service, 7 unlock, 8 network cleartext, 9 new credentials, 10 Remote Desktop, 11 cached interactive).

LogSecurity
SourceMicrosoft-Windows-Security-Auditing
AreaSign-in

What to check

Filter on high-value accounts and on Elevated Token = Yes for admin logons. Treat batch (4) or service (5) logons by domain admins, and type 10 logons without Restricted Admin where it is mandated, as worth investigating.

Codes you'll see in this event

CodeMeaning
2Interactive: signed in at the console.
3Network: for example a file share or remote management.
4Batch: scheduled task or batch server.
5Service: started by the Service Control Manager.
7Unlock: workstation unlocked.
8NetworkCleartext: password passed to the authentication package unhashed.
9NewCredentials: cloned token with new credentials for outbound connections (for example RunAs /netonly).
10RemoteInteractive: Remote Desktop or Terminal Services.
11CachedInteractive: cached credentials, no DC contacted.

Find it with PowerShell

Run on the machine that logs it, as an administrator.

powershell2 lines
Get-WinEvent -FilterHashtable @{ LogName = 'Security'; Id = 4624 } -MaxEvents 50 |
    Format-List TimeCreated, Id, Message

Hunt for it in Sentinel or Log Analytics

Security events land in the SecurityEvent table when you collect them with the Windows Security Events connector or a data collection rule.

kql5 lines
SecurityEvent
| where TimeGenerated > ago(7d)
| where EventID == 4624
| project TimeGenerated, Computer, Account, Activity
| order by TimeGenerated desc

Related Sign-in events

Search all 123 event IDs →