CyberKit

Event IDs

Security event 7045

A service was installed in the system

Channel: System. Category: Service Installation (Service Control Manager).

What it records

Logged to the System channel (source: Service Control Manager) whenever a new service is installed, recording the Service Name, the full Service File Name/ImagePath to its executable, Service Type, Service Start Type, and the Service Account it runs as.

Why it matters

Because it's written to the System log by the Service Control Manager itself, it is enabled by default on every Windows system with no advanced audit-policy configuration required, making it one of the most reliable, universally available artifacts for detecting service-based persistence and lateral movement. Classic example: PsExec drops PSEXESVC.exe as a temporary service on the target, generating a 7045 that is a strong indicator of PsExec-based lateral movement. The ImagePath is the primary triage field: services pointing at Temp, AppData, or other non-standard paths are a strong red flag.

What triggers it

Legitimate software, driver, and Windows Update installations, alongside malicious service creation for persistence, privilege escalation, or lateral movement.

Fields that carry the answer

Key fields
FieldWhat it tells you
Service NameThe display name of the newly installed service. Compare against known-good service names for anything unfamiliar or randomly generated.
Service File NameThe full path to the service's executable (ImagePath): the primary triage field; a path in Temp, AppData, ProgramData, or another non-standard location is a strong red flag, and PsExec's PSEXESVC.exe is the classic example.
Service Start TypeWhether the service is set to auto-start, demand-start, etc.. Auto-start on an unfamiliar service indicates an intent to persist across reboots.
Service AccountThe account the service runs as: a service running as LocalSystem gives an attacker SYSTEM-level execution, making this the field that reveals the privilege gained.

In practice

The System log shows a new service named "WinUpdateSvc" with Service File Name C:\Windows\Temp\svc.exe, Service Start Type "auto start," and Service Account "LocalSystem," created moments after a PsExec-style connection under CORP\jsmith's session: a classic lateral-movement persistence pattern where the ImagePath and account are the first things worth pivoting on.

Sample record

A service was installed in the system.

Service Name:  WinUpdateSvc
Service File Name:  C:\Windows\Temp\svc.exe
Service Type:  user mode service
Service Start Type:  auto start
Service Account:  LocalSystem

ATT&CK techniques

Sources

Paste a record into Event XML or open a log in EVTX Reader.