Detectionhightest
User Couldn't Call a Privileged Service 'LsaRegisterLogonProcess'
The 'LsaRegisterLogonProcess' function verifies that the application making the function call is a logon process by checking that it has the SeTcbPrivilege privilege set. Possible Rubeus tries to get a handle to LSA.
Convert In Phoenix Studio
Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.
Launch
Roberto Rodriguez (Cyb3rWard0g), Ilyas Ochkov, oscd.communityCreated Thu Oct 24Updated Sun Dec 256daac7fc-77d1-449a-a71a-e6b4d59a0e54windows
Log Source
Windowssecurity
ProductWindows← raw: windows
Servicesecurity← raw: security
Detection Logic
Detection Logic1 selector
detection:
selection:
EventID: 4673
Service: 'LsaRegisterLogonProcess()'
Keywords: '0x8010000000000000' # failure
condition: selectionFalse Positives
Unknown
False positive likelihood has not been assessed. Additional context may be needed during triage.
References
MITRE ATT&CK
Rule Metadata
Rule ID
6daac7fc-77d1-449a-a71a-e6b4d59a0e54
Status
test
Level
high
Type
Detection
Created
Thu Oct 24
Modified
Sun Dec 25
Path
rules/windows/builtin/security/win_security_user_couldnt_call_priv_service_lsaregisterlogonprocess.yml
Raw Tags
attack.credential-accessattack.lateral-movementattack.privilege-escalationattack.t1558.003