Skip to content

Windows Event ID 4611: A trusted logon process has been registered with the LSA

Written when a process that handles logon is confirmed and registered with the LSA as a trusted logon process. From then on, logon requests from that source are accepted.

Overview

The subcategory is Audit Security System Extension. A logon process is a trusted OS component (such as Winlogon) that coordinates the various logon methods (network, interactive, and so on). Strictly speaking the event comes not from the registration itself but from a confirmation that the process is a trusted logon process. It is seen during OS startup and during user logon and authentication.

How it is triggered

  • Initialization at system startup.
  • When a logon process is confirmed by the LSA during logon and authentication.
  • It is normally driven by the SYSTEM account (an internal OS account), registering legitimate processes such as Winlogon.

Security review points

  • Report any case where the subject Subject\Security ID is not SYSTEM. It can indicate that a non-legitimate account is trying to register a logon process.
  • If Logon Process Name is anything other than a known legitimate process (Winlogon, User32, and so on), check it against an allow list. Registration of a suspicious logon process can be a move to interpose on the authentication path.

Notes for log review

  • It is mostly informational and appears regularly with startup and logon. Because the values (process name, subject) are stable, watching for deviations with an allow list is practical.
  • Narrowing to “subject is not SYSTEM” tends to leave only what is worth investigating.

MITRE ATT&CK mapping

TechniqueTacticWhat this event shows
T1558 Steal or Forge Kerberos TicketsCredential AccessRubeus registers the logon process User32LogonProcesss to get an LSA handle for ticket operations. Names outside the known legitimate set are the lead

Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.

Detection rules

SigmaHQ has 1 public detection rule that uses this event ID as a condition.

RuleTypeSeverity
Register new Logon Process by RubeusSigmaHigh

Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.

Key fields

FieldMeaning
Subject\Security IDThe subject that performed the registration; usually SYSTEM
Logon Process NameThe registered logon process name (for example, Winlogon)
Logon IDUsed to match other events in the same session (such as 4624)

References