Skip to content
CyberSimStart training

Windows Security log

4624 An account was successfully logged on.

A logon session was created on the computer that logs the event. The logon type says how: at the keyboard, over the network, as a service, through Remote Desktop. It is the event every investigation of an account starts from.

Fields to read

FieldWhat it tells you
TargetUserNameThe account that logged on.
LogonType2 interactive, 3 network, 4 batch, 5 service, 7 unlock, 10 Remote Desktop, 11 cached interactive.
IpAddress / WorkstationNameWhere the logon came from (for network and Remote Desktop logons).
AuthenticationPackageNameKerberos or NTLM. NTLM between domain computers deserves a second look.
ElevatedTokenWhether the session got a full administrator token.
TargetLogonIdThe session ID: links this logon to the 4672, 4688 and 4634 events of the same session.

Normal

  • Type 3 network logons all day long: file shares, printers, domain controllers.
  • Types 2, 7 and 11 on a user’s own laptop during working hours.
  • Type 5 service logons by service accounts when services start.

Suspicious

  • Type 10 (Remote Desktop) from the internet or from a host that never connects to this one.
  • A success right after a run of 4625 failures for the same account or from the same address.
  • One account logging on to many hosts over the network in a short time (lateral movement).
  • Administrator accounts logging on to ordinary workstations, or at hours they never work.

Find it

Microsoft Sentinel (KQL)

SecurityEvent
| where EventID == 4624

Splunk (SPL)

index=wineventlog source="XmlWinEventLog:Security" EventCode=4624

Table, index and source names as CyberSim uses them; your workspace may name them differently.

Where you meet it in CyberSim

Cases

Alerts in the shift

The L3 war room

It is also part of the background activity of every investigation window: the noise you search through.

ATT&CK techniques it can show

In the glossary

Other Security events

Source: Microsoft Learn: event 4624