Security event 4768
A Kerberos authentication ticket (TGT) was requested
Channel: Security. Category: Account Logon (Audit Kerberos Authentication Service).
What it records
Logged only on a domain controller every time the Key Distribution Center (KDC) issues, or fails to issue, a Kerberos Ticket Granting Ticket (TGT). Records the requesting account, client IP, pre-authentication type, ticket/session encryption types, and a Result Code identifying the reason for any failure. Result Codes 0x10 and 0x18 never appear here. Microsoft's documentation states those failures generate event 4771 instead.
Why it matters
The starting point of Kerberos authentication on the wire, and central to detecting AS-REP Roasting (Pre-Authentication Type value 0, tied to accounts configured with 'Do not require Kerberos preauthentication'), weak-encryption (DES/RC4) usage, and account-enumeration/brute-force patterns via the Result Code.
What triggers it
Any interactive, network, or service Kerberos logon to a domain account. A spike of Result Code 0x6 (client not found: nonexistent username) can indicate account enumeration; Pre-Authentication Type 0 flags an account vulnerable to AS-REP Roasting.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Account Information > Account Name | The account for which the TGT was requested: the core identity to pivot on for all Kerberos authentication activity. |
| Network Information > Client Address | The source IP of the TGT request: the pivot field for isolating where brute-force, spray, or enumeration traffic against Kerberos is coming from. |
| Pre-Authentication Type | A value of 0 means the account authenticated without pre-authentication: the direct indicator of an AS-REP Roastable account (one configured with 'Do not require Kerberos preauthentication'). |
| Ticket Encryption Type | 0x1/0x3 mean the deprecated DES algorithm was used, and anything other than 0x11/0x12 (AES) on a modern OS is worth flagging. Weak Kerberos encryption is a downgrade-attack target. |
| Result Code | The KDC error code for a failed request: a spike of 0x6 (unknown username) signals account enumeration, while repeated 0x12 (revoked credentials) failures across many accounts from one source signals a brute-force/spray attempt. |
In practice
CORP\jdoe authenticates interactively at their workstation; Account Information > Account Name shows CORP\jdoe, Network Information > Client Address shows 198.51.100.23, Pre-Authentication Type is 2 (normal), Ticket Encryption Type is 0x12 (AES256), and Result Code is 0x0: a routine successful TGT issuance. The same event with Pre-Authentication Type 0 on a service account instead flags it as AS-REP Roastable.
Sample record
A Kerberos authentication ticket (TGT) was requested. Authentication Ticket Request: Account Information: Account Name: jdoe Supplied Realm Name: CORP.LOCAL User ID: CORP\jdoe Service Information: Service Name: krbtgt Service ID: CORP\krbtgt Network Information: Client Address: ::ffff:192.0.2.10 Client Port: 0 Additional Information: Ticket Options: 0x40810010 Result Code: 0x0 Ticket Encryption Type: 0x12 Pre-Authentication Type: 2 Certificate Information: Certificate Issuer Name: - Certificate Serial Number: - Certificate Thumbprint: -
ATT&CK techniques
- T1558.004: T1558.004
Sources
Paste a record into Event XML or open a log in EVTX Reader.