Windows Kerberoasting Initial Query: Successful 4769 RC4 Service Requests with Filters

Collects successful Windows 4769 RC4 service-ticket requests while excluding krbtgt and computer/service account patterns for kerberoasting triage.

FreeReviewedSigma · Medium · v2
Product
windows
Service
security
Author
@kostastsale (SigmaHQ), DRL 1.1
Published
2022-01-21
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 gathers telemetry related to potential Kerberoasting by selecting successful Windows Security Event ID 4769 service ticket requests that use RC4 ticket encryption (TicketEncryptionType 0x17). It filters out requests for service names ending in krbtgt and machine/service account patterns (e.g., usernames containing '$@' and service names ending with '$') to reduce noise from normal Kerberos traffic. It relies on Windows Security log fields EventID, Status, ServiceName, TicketEncryptionType, and TargetUserName for its matches.

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)
Windows Kerberoasting Initial Query: Successful 4769 RC4 Service Requests with Filters
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.