Windows Security 4768 — Kerberos TGT request

Source and collection

Windows Event Log: Security; archived .evtx is binary, while this fixture is an XML event export.

Configure Audit Kerberos Authentication Service. Read with Get-WinEvent and preserve provider, event ID, version, computer and record ID.

Native example and provenance

publisher documentation example. Published example; no independent capture provenance claimed.

Original publisher / pinned upstream fixture — preformatted example 1

One complete record selected; values unchanged.

Download the exact sample · Offline research kit

SHA-256: db6b0cdeb09eb4b63891c9efec0a44b3fffefa98da3d310fde496a2511b04556

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
  <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /> 
  <EventID>4768</EventID> 
  <Version>2</Version> 
  <Level>0</Level> 
  <Task>14339</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8020000000000000</Keywords> 
  <TimeCreated SystemTime="2025-02-26T00:11:39.8853919Z" /> 
  <EventRecordID>2868</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="696" ThreadID="2564" /> 
  <Channel>Security</Channel> 
  <Computer>DC01.contoso.local</Computer> 
  <Security /> 
  </System>
  <EventData>
  <Data Name="TargetUserName">duser</Data> 
  <Data Name="TargetDomainName">CONTOSO.LOCAL</Data> 
  <Data Name="TargetSid">S-1-5-21-3114123713-1067509961-1646476345-1104</Data> 
  <Data Name="ServiceName">krbtgt</Data> 
  <Data Name="ServiceSid">S-1-5-21-3114123713-1067509961-1646476345-502</Data> 
  <Data Name="TicketOptions">0x40810010</Data> 
  <Data Name="Status">0x0</Data> 
  <Data Name="TicketEncryptionType">0x12</Data> 
  <Data Name="PreAuthType">2</Data> 
  <Data Name="IpAddress">::ffff:172.27.248.104</Data> 
  <Data Name="IpPort">54393</Data> 
  <Data Name="CertIssuerName" /> 
  <Data Name="CertSerialNumber" /> 
  <Data Name="CertThumbprint" /> 
  <Data Name="ResponseTicket">j2P3Uf3sxhIsE6N4+wMt0WDyhXdVBUKMoWzmRRpxqaI=</Data> 
  <Data Name="AccountSupportedEncryptionTypes">0x27 (DES, RC4, AES-Sk)</Data> 
  <Data Name="AccountAvailableKeys">AES-SHA1, RC4</Data> 
  <Data Name="ServiceSupportedEncryptionTypes">0x1F (DES, RC4, AES128-SHA96, AES256-SHA96)</Data> 
  <Data Name="ServiceAvailableKeys">AES-SHA1, RC4</Data> 
  <Data Name="DCSupportedEncryptionTypes">0x1F (DES, RC4, AES128-SHA96, AES256-SHA96)</Data> 
  <Data Name="DCAvailableKeys">AES-SHA1, RC4</Data> 
  <Data Name="ClientAdvertizedEncryptionTypes">AES256-CTS-HMAC-SHA1-96 RC4-HMAC-NT RC4-HMAC-OLD RC4-MD4 RC4-HMAC-NT-EXP RC4-HMAC-OLD-EXP</Data> 
  <Data Name="SessionKeyEncryptionType">0x12</Data> 
  <Data Name="PreAuthEncryptionType">0x12</Data> 
  </EventData>
  </Event>

Structure and field interpretation

System/EventID

Event identifier within the named provider.

System/Version

Version of this event layout.

System/TimeCreated/@SystemTime

Event timestamp in UTC.

EventData

Named fields; use names, not positional array indices.

Relevant fields

TargetUserName, IpAddress, TicketEncryptionType, Status

Investigation uses

• Compare client address, account and encryption information against domain policy and related Kerberos events.
• Compare event time with ingestion time and retain the original XML for a reviewable evidence trail.

Validation boundaries

Event versions and fields vary with Windows updates; this preserved documentation example is not a promise of the latest field set. This sample uses event version 2.

This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.

For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.

Related sources

• Windows Security 4624 — Successful logon
• Windows Security 4625 — Failed logon
• Windows Security 4688 — Process creation
• Windows Security 4698 — Scheduled task created
• Windows Security 4720 — User account created
• Windows Security 4732 — Member added to local security group

Ecosystem connections

• Telemetry Library — ATT&CK data components
• Detection Rules — candidate detection content
• Threat hunting — from intelligence to validated defense
• Practical security learning paths
• AdversaryGraph — evidence-led investigation

• DC0084 — conceptual telemetry association, not coverage proof

References

• 4768(S, F) A Kerberos authentication ticket (TGT) was requested. - Windows 10 | Microsoft Learn

Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.