Windows Event ID 4769: A Kerberos service ticket was requested
Written when the KDC issues a Kerberos service ticket (TGS). It is the most important Kerberos monitoring event, usable to detect Kerberoasting (cracking service-account passwords).
Overview
The subcategory is Audit Kerberos Service Ticket Operations. It is generated whenever the KDC receives and issues a service ticket (TGS) request for a specific service (SPN: Service Principal Name). It includes the requesting account, target service name, encryption type, and source IP. Note that on Windows Server 2016 and later, the January 14, 2025 or later cumulative update switches the event to an updated format.
How it is triggered
- When a user uses a TGT (4768) to request the service ticket needed to access a particular service.
- It occurs constantly during legitimate resource access (file shares, SQL, HTTP, and so on).
Security review points
- Kerberoasting: an attacker requests many tickets for SPN-bearing service accounts and cracks the encrypted part offline to recover the password. A service-ticket request with
Ticket Encryption Typeof0x17(RC4) is a red flag in a modern AES-default environment; attackers often deliberately request the more crackable RC4. - Note patterns such as one account requesting tickets for many different SPNs in a short time, or requests for the SPN of high-value service accounts. Requests for
krbtgtor computer accounts (ending in$) are normal and are usually excluded from Kerberoasting detection. - Also check the
Failure Code(such as0x1b). Correlate with the TGT 4768 to track the requesting user’s full activity.
Notes for log review
- It is a normal event produced in huge volume on DCs and service servers. It becomes Kerberoasting detection only with narrowing to
RC4 (0x17)and the correlation of “one user requesting many SPNs in a short time.” - Standardizing the environment to AES-only makes RC4 requests themselves stand out as anomalies, improving detection precision.
MITRE ATT&CK mapping
| Technique | Tactic | What this event shows |
|---|---|---|
| T1558.003 Kerberoasting | Credential Access | RC4 (0x17) service tickets, or requests for many SPNs in a short time |
Mapping as of ATT&CK v19.2. ATT&CK detection strategy DET0157 (T1558.003) also lists this event ID as a log source. To search by technique, see the ATT&CK reverse lookup.
Detection rules
SigmaHQ has 3 and Microsoft Sentinel has 3 public detection rules that use this event ID as a condition.
| Rule | Type | Severity |
|---|---|---|
| Kerberos Manipulation | Sigma | High |
| Kerberoasting Activity - Initial Query | Sigma | Medium |
| Potential Kerberoasting | Sentinel analytics rule | Medium |
| Suspicious Kerberos RC4 Ticket Encryption | Sigma | Medium |
| Failed Login Attempt by Expired account | Sentinel hunting query | - |
| Kerberoast burst followed by cloud sign-in | Sentinel hunting query | - |
Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.
Key fields
| Field | Meaning |
|---|---|
Account Name | The account that requested the service ticket |
Service Name / Service ID | The target service (SPN) |
Ticket Encryption Type | 0x17 (RC4) is a Kerberoasting red flag; 0x12 is AES256 |
Client Address | The requesting IP |
Failure Code | The failure reason |
Glossary
- Kerberoasting — an attack that obtains tickets for SPN-bearing service accounts and cracks the password offline. Service accounts with weak passwords are the target.
- SPN (Service Principal Name) — a name that uniquely identifies a service; it is the destination of a ticket request.