Detect Kerberos Pass-the-Ticket (PtT) attacks by analyzing Windows Event IDs 4768, 4769, and 4771 for anomalous ticket usage patterns, with detection queries for Splunk and Elastic SIEM.
Detect Kerberos Pass-the-Ticket (PtT) attacks by analyzing Windows Event IDs 4768, 4769, and 4771 for anomalous ticket usage patterns, with detection queries for Splunk and Elastic SIEM.
Use when investigating incidents involving stolen or replayed Kerberos tickets, building detection rules or threat hunting queries for ticket abuse, or validating SOC monitoring coverage for credential-theft attack techniques.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars32.4K
LicenseLICENSE
Default branchmain
Open issues20
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Version1.0
LicenseApache-2.0
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,868 B
docsSUMMARY.md454 B
History
First seen on skills.sh
First recorded snapshot · 79 installs
SKILL.md
Detecting Pass-the-Ticket Attacks
Overview
Pass-the-Ticket (PtT) is a credential theft technique (MITRE ATT&CK T1550.003) where adversaries steal Kerberos tickets (TGT or TGS) from one system and replay them on another to authenticate without knowing the user's password. This skill teaches detection of PtT attacks by correlating Windows Security Event IDs 4768 (TGT request), 4769 (TGS request), and 4771 (pre-authentication failure) for anomalies such as ticket reuse across different hosts, RC4 encryption downgrades, and unusual service ticket request volumes.
When to Use
When investigating security incidents that require detecting pass the ticket attacks
When building detection rules or threat hunting queries for this domain
When SOC analysts need structured procedures for this analysis type
When validating security monitoring coverage for related attack techniques
Prerequisites
Windows Domain Controller with advanced audit policy enabled (Audit Kerberos Authentication Service, Audit Kerberos Service Ticket Operations)
Splunk or Elastic SIEM ingesting Windows Security event logs
Sysmon deployed on endpoints for supplementary process telemetry
Python 3.8+ with requests library
Steps
Enable Kerberos audit logging on Domain Controllers via Group Policy
Forward Event IDs 4768, 4769, and 4771 to SIEM platform
Deploy detection rules for RC4 encryption downgrade (TicketEncryptionType 0x17)
Create correlation rule for ticket reuse across multiple source IPs
Build baseline of normal TGS request volume per user/host
Alert on standard deviation anomalies in ticket request patterns
Investigate flagged events with enrichment from Active Directory
Expected Output
JSON report containing detected PtT indicators including anomalous ticket requests, RC4 downgrades, cross-host ticket reuse events, and risk-scored users with MITRE ATT&CK technique mapping.