4608 Security log · System info severity low volume

Windows Event ID 4608 — Windows is starting up

Security subsystem started. Generated at boot.

Why event 4608 matters

Use to establish boot timeline. Correlate with 6005 (System log). Unexpected Windows restarts warrant review.

How to detect it

No standalone alerting. Use for forensic timeline reconstruction.

Log source
Security
Advanced Audit Policy — enable the 'System' subcategory (Success and/or Failure).
Fields to pivot on
SubjectUserNameTargetUserNameLogonTypeIpAddressWorkstationName

Detection queries

Starting points — adapt the log source, projected fields and thresholds for your environment.

Sentinel / Defender KQL
SecurityEvent
| where EventID == 4608   // Windows is starting up
| project TimeGenerated, Computer, SubjectUserName, TargetUserName, LogonType, IpAddress, WorkstationName
| sort by TimeGenerated desc
Splunk SPL
index=* sourcetype="WinEventLog:Security" EventCode=4608
| stats count earliest(_time) as first_seen latest(_time) as last_seen by ComputerName
| sort - count   `# Windows is starting up — add EventData fields: SubjectUserName, TargetUserName, LogonType, IpAddress`
Hunt event 4608 in Sentinel/Defender →
Build a KQL query for this event in the KQL Query Builder.
Search all event IDs →
Open the interactive Windows Event ID lookup.

Related System events

4616 The system time was changed 4621 Administrator recovered system from CrashOnAuditFail

Frequently asked questions

What is Windows Event ID 4608?

Windows is starting up. Security subsystem started. Generated at boot.

Which log records event 4608?

Event 4608 is written to the Security channel by Microsoft-Windows-Security-Auditing. Advanced Audit Policy — enable the 'System' subcategory (Success and/or Failure).

How do you detect activity around event 4608?

No standalone alerting. Use for forensic timeline reconstruction.