Security event 4769
A Kerberos service ticket was requested
Channel: Security. Category: Account Logon (Audit Kerberos Service Ticket Operations).
What it records
Logged only on a domain controller each time the KDC receives a Kerberos Ticket Granting Service (TGS) ticket request. Records the requesting account, the target Service Name/SID, client IP, ticket encryption type, and a Failure Code for unsuccessful requests. Microsoft's own guidance notes that Failure Code 0x20 (an expired service ticket) is routine and has little to no security relevance.
Why it matters
The definitive event for detecting Kerberoasting: a TGS request using RC4 (0x17) ticket encryption for a Service-Principal-Name-bearing account, especially many distinct Service Names requested from one source in a short window, is the classic offline-cracking signature. Also useful for confirming exactly which SPN-registered services an account accessed.
What triggers it
Every access to an SPN-registered service (file shares, SQL Server, an IIS site with an SPN, etc.) generates this routinely. A burst of requests for many different Service Names by a single account in a short time is the hallmark of a Kerberoasting attempt.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Account Information > Account Name | The account that requested the service ticket: the identity to pivot on when investigating Kerberoasting or lateral movement. |
| Service Information > Service Name | The SPN-registered account or computer the ticket was requested for: a single account requesting tickets for many distinct Service Names in a short window is the signature of Kerberoasting. |
| Network Information > Client Address | The source IP of the TGS request. Pivot point for isolating the origin of a Kerberoasting sweep or unusual service access. |
| Ticket Encryption Type | RC4 (0x17) ticket encryption for a service account is the classic Kerberoasting signature, since RC4-encrypted tickets are far cheaper to crack offline than AES. |
| Failure Code | Non-zero indicates a denied service-ticket request; Microsoft notes 0x20 (expired ticket) is routine, so filter that out and focus on other codes when triaging. |
In practice
CORP\jsmith requests a service ticket for the SPN 'MSSQLSvc/sql01.corp.local:1433'; Account Information > Account Name shows CORP\jsmith, Service Information > Service Name shows sql01$, Network Information > Client Address shows 203.0.113.15, and Ticket Encryption Type shows 0x17 (RC4). Routine SQL access on its own, but that same RC4 encryption appearing across many distinct Service Names requested by one account in a short window is the signature of Kerberoasting.
Sample record
A Kerberos service ticket was requested.
Account Information:
Account Name: jdoe@corp.example.com
Account Domain: CORP.LOCAL
Logon GUID: {00000000-0000-0000-0000-000000000000}
Service Information:
Service Name: SQLSvc01
Service ID: CORP\SQLSvc01
Network Information:
Client Address: ::ffff:192.0.2.15
Client Port: 49812
Additional Information:
Ticket Options: 0x40810000
Ticket Encryption Type: 0x17
Failure Code: 0x0
Transited Services: -ATT&CK techniques
- T1558.003: T1558.003
Sources
Paste a record into Event XML or open a log in EVTX Reader.