Service Creation via Local Kerberos Authenticationedit

Identifies a suspicious local successful logon event where the Logon Package is Kerberos, the remote address is set to localhost, followed by a sevice creation from the same LogonId. This may indicate an attempt to leverage a Kerberos relay attack variant that can be used to elevate privilege locally from a domain joined user to local System privileges.

Rule type: eql

Rule indices:

  • winlogbeat-*
  • logs-system.*

Severity: high

Risk score: 73

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100



  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Privilege Escalation
  • Credential Access

Version: 2 (version history)

Added (Elastic Stack release): 8.3.0

Last modified (Elastic Stack release): 8.4.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule queryedit

sequence by with maxspan=5m [authentication where /* event
4624 need to be logged */ event.action == "logged-in" and
event.outcome == "success" and /* authenticate locally using
relayed kerberos Ticket */
winlog.event_data.AuthenticationPackageName :"Kerberos" and
winlog.logon.type == "Network" and cidrmatch(source.ip,
"", "::1") and source.port > 0] by
winlog.event_data.TargetLogonId [any where /* event 4697 need to
be logged */ event.action : "service-installed"] by

Threat mappingedit


Rule version historyedit

Version 2 (8.4.0 release)
  • Formatting only