Uncommon Outbound Kerberos Port 88 Network Connections (Windows Security Event 5156)

Alerts on rare outbound Kerberos (port 88) connections from non-browser/non-lsass processes using Windows Event 5156.

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

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows Security Event 5156 instances where an outbound connection targets destination port 88, which indicates Kerberos traffic to an external host. Such activity can be relevant for attacker behaviors like lateral movement or credential-access techniques involving delegation. The detection relies on event telemetry containing the process image path and destination port, and it excludes connections originating from typical local system paths used by lsass.exe and common browser executables.

Related detections9 linkedT1558.003 — drag to rearrange
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
Suspicious SQL Service Principal Name Enumeration via Setspn
Windows: Suspicious Kerberos Ticket Requests from PowerShell Using KerberosRequestorSecurityToken
Windows Process Creation: RemoteKrbRelay Kerberos Relay Tool Execution
Windows Kerberos KDC Key Distribution Failure: No Suitable Encryption Key or Unsupported EType
Rubeus HackTool Execution via PowerShell ScriptBlock Flags (Windows)
Uncommon Outbound Kerberos Port 88 Network Connections (Windows Security Event 5156)
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.