Kerberos policy was changed
Domain Kerberos ticket lifetime, renewal, or clock skew settings were altered.
Event ID 4713 triggers when domain-wide Kerberos policy parameters (such as `MaxServiceTicketAge`, `MaxTicketAge`, or `MaxClockSkew`) are modified in Group Policy. Threat actors sometimes extend service ticket lifetimes or clock skew tolerances to facilitate long-lived forged Kerberos tickets (Golden/Silver tickets).
Failure Reason / Root Cause:
Modification of domain Kerberos policy values via domain security policy.
Raw Event XML snippet
<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>4713</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2026-07-17T09:54:44.885Z" />
<EventRecordID>1048576</EventRecordID>
<Correlation />
<Execution ProcessID="612" ThreadID="1024" />
<Channel>Security</Channel>
<Computer>DC01.enterprise.internal</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">SYSTEM</Data>
<Data Name="SubjectDomainName">NT AUTHORITY</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<!-- Event telemetry fields specific to Kerberos policy was changed -->
</EventData>
</Event>MITRE ATT&CK mapping
| ID | Technique | Tactic |
|---|---|---|
T1098 | Account Manipulation | Persistence |
Recommended actions
- Verify that changes to Kerberos ticket lifetimes align with authorized Group Policy administration schedules.
- Ensure `MaxServiceTicketAge` remains at or below standard defaults (600 minutes).