Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / ACTIVE DIRECTORY / RELAY ATTACKS

Kerberos Relay

This note documents detection patterns related to Kerberos Relay within Active Directory environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Security4769Kerberos service ticket request (TGS)CriticalPrimary signal when Kerberos tickets are requested for services such as LDAP, CIFS, or HOST unexpectedly. Review ServiceName, ClientAddress, TicketOptions, and TargetUserName.
Security4768Kerberos TGT requestHighMay appear when attacker authenticates before performing relay activity. Useful for establishing session origin.
Security4624Successful logonHighLook for LogonType 3 (network) originating from unusual hosts immediately after Kerberos ticket issuance.
Security4672Special privileges assignedHighPrivileged sessions following Kerberos authentication may indicate successful relay leading to privilege escalation.
Security4688Process creationMediumMay reveal execution of tools such as krbrelayx or Rubeus.
Sysmon1Process creationCriticalExecution of Kerberos relay tooling (krbrelayx, Rubeus, Impacket utilities).
Sysmon3Network connectionHighSuspicious LDAP/SMB connections following Kerberos ticket acquisition.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Authentication coercion preceding Kerberos ticketPrinterBug, PetitPotam, DFSCoerce, or other coercion attacksCriticalThese attacks force a host to authenticate to attacker-controlled system which enables relay.
Kerberos authentication to unexpected servicesService tickets requested for LDAP or CIFS on domain controllers unexpectedlyHighOften indicates ticket relay attempt.
Unusual host performing service ticket requestsWorkstation requesting tickets for services normally accessed by serversHighSuggests attacker-controlled relay host.
Service ticket reuse across systemsSame Kerberos ticket used across multiple hosts shortly after issuanceHighMay indicate relay or ticket forwarding abuse.
Privileged changes following authenticationACL modifications, new machine accounts, or delegation changesCriticalIndicates attacker leveraged relayed Kerberos authentication.

Common Tools

ToolUsage
krbrelayxRelays Kerberos authentication to LDAP or SMB services.
ImpacketContains Kerberos relay capabilities and supporting tooling.
RubeusUsed to manipulate Kerberos tickets during relay attacks.
PrinterBugCoerces authentication to attacker-controlled host.
PetitPotamTriggers NTLM/Kerberos authentication from domain controllers.
CoercerFramework for automating authentication coercion.

Relevant Artifacts

  • Domain controller Security logs (4768, 4769, 4624)
  • Sysmon logs (1, 3)
  • Kerberos operational logs
  • LDAP service logs
  • SMB authentication logs
  • EDR telemetry detecting relay tooling
  • Network telemetry showing Kerberos authentication flows
  • Prefetch artifacts for Kerberos exploitation tools

MITRE ATT&CK References

  • T1557 Adversary-in-the-Middle
  • T1557.003 Kerberos Relay
  • T1558 Steal or Forge Kerberos Tickets
  • T1078 Valid Accounts

Decision Tree

  1. Is the suspicious event present?
    • Identify Kerberos service ticket requests (4769) for unusual services.
  2. What host generated the event?
    • Determine whether request originated from workstation rather than expected service host.
  3. Is the account expected to perform this action?
    • Verify whether the account normally authenticates to the requested service.
  4. Pivot:
    • Source host → inspect processes for krbrelayx or Kerberos manipulation tools.
    • Account → review privilege escalation activity.
    • Network → inspect authentication coercion preceding the ticket request.
  5. Confirm exploitation
    • Determine whether attacker performed administrative actions following relay.

Example Detection Templates

KQL

SecurityEvent
| where EventID == 4769
| summarize count() by ServiceName, TargetUserName, ClientAddress, bin(TimeGenerated, 5m)
| order by count_ desc
SecurityEvent
| where EventID == 4624
| where LogonType == 3
| project TimeGenerated, TargetUserName, IpAddress, WorkstationName

EQL

any where event.code == "4769"

Sigma

title: Suspicious Kerberos Service Ticket Activity
id: kerberos-relay-detection
status: experimental
description: Detects abnormal Kerberos service ticket requests potentially associated with Kerberos relay attacks
logsource:
  product: windows
  service: security
detection:
  selection:
    EventID: 4769
  condition: selection
fields:
  - ServiceName
  - TargetUserName
  - ClientAddress
falsepositives:
  - Legitimate service authentication patterns
level: medium
tags:
  - attack.credential_access
  - attack.t1557.003

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
LDAP signingRequire LDAP signing and channel bindingHighPrevents relay to LDAP services.
SMB signingEnforce SMB signingHighPrevents Kerberos relay to SMB services.
Delegation restrictionsRestrict delegation settings across domainHighLimits abuse paths.
Network monitoringMonitor Kerberos authentication patternsMediumDetects unusual ticket requests.
Service hardeningRestrict services that accept delegated authenticationMediumReduces potential relay targets.