huntrule

Windows Security 4673: Failed LsaRegisterLogonProcess Handle Registration

Alerts on failed attempts to call LsaRegisterLogonProcess() in Windows Security (Event 4673), tied to the SeTcbPrivilege requirement.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Roberto Rodriguez (source), Ilyas Ochkov (rule), oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-24
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Cred Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows Security events where a process attempts to call LsaRegisterLogonProcess() and the operation fails (Keywords indicate failure). Attackers may probe for access to LSA-related functionality to support credential access or lateral movement paths, including attempts to interact with logon-process registration mechanisms. Telemetry relies on EventID 4673 from the Windows Security log with the specified service name and failure keyword value.

Reporting behind it

Related detections9 linkedT1558.003 — drag to rearrange
Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters
Possible Kerberoasting via RC4 Service Ticket Requests
Suspicious LDAP Query Enumerating Kerberos Preauth Disabled Accounts with Whitespace Evasion
Suspicious Kerberoasting LDAP Search Filter for Service Principal Names
Suspicious Kerberoasting via RC4 Service Ticket Request for MSSQLSvc SPN (via security)
Malicious Kerberos Ticket File Creation Indicating Credential Theft (via file_event)
Suspicious Kerberoasting via setspn Service Principal Query
Masquerading Kerberos Ticket Abuse via Rubeus (via process_creation)
Possible Targeted Kerberoasting via servicePrincipalName Modification
Windows Security 4673: Failed LsaRegisterLogonProcess Handle Registration
Pivot detection · T1558.003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.