
Detecting Pass-the-Ticket Attacks
FreeIdentify and analyze Kerberos PtT attacks effectively.
Free · Opens the source repo
What Detecting Pass-the-Ticket Attacks does
The Detecting Pass-the-Ticket Attacks skill is designed for security professionals looking to enhance their incident response capabilities regarding Kerberos credential theft. By analyzing specific Windows Security Event IDs—4768, 4769, and 4771—this skill helps in identifying anomalous ticket usage patterns indicative of Pass-the-Ticket (PtT) attacks. These attacks allow adversaries to authenticate on systems without needing the user's password, making detection critical in maintaining security. The skill provides structured procedures for correlating events and identifying abnormal behaviors such as ticket reuse across different hosts and unusual service ticket request volumes.
This skill is particularly useful for Security Operations Center (SOC) analysts and incident responders. It aids in the investigation of security incidents involving stolen or replayed Kerberos tickets, and it can be employed to build detection rules or threat hunting queries tailored to this type of credential abuse. Furthermore, it serves as a validation tool for assessing the effectiveness of existing security monitoring coverage against credential-theft attack techniques.
To utilize this skill, users need a Windows Domain Controller with advanced audit policies enabled, along with a SIEM solution like Splunk or Elastic that ingests Windows Security event logs. The skill also requires Python 3.8+ and the requests library to function properly. By following the provided steps, users can set up detection rules, create correlation rules, and establish baselines for normal ticket request volumes, leading to actionable alerts on potential threats.
Expected outputs include a JSON report detailing detected indicators of PtT attacks, including anomalies in ticket requests and risk-scored users mapped to the MITRE ATT&CK framework. This comprehensive approach not only enhances detection capabilities but also supports a proactive security posture against credential theft.
When to use it
Use this skill when investigating security incidents involving Kerberos credential theft or when building detection rules for PtT attacks.
When not to use it
This skill may not be suitable for environments without Windows Domain Controllers or where Kerberos authentication is not utilized.
What you can build with it
Incident Investigation
Use this skill to analyze Windows event logs when investigating a suspected Pass-the-Ticket attack.
Building Detection Rules
Leverage the skill to create detection rules tailored for identifying anomalous Kerberos ticket usage.
Validating SOC Coverage
Employ this skill to assess and validate the effectiveness of your security monitoring against credential theft techniques.
How to install Detecting Pass-the-Ticket Attacks
View source1. Install with the skills CLI
npx skills add mukul975/anthropic-cybersecurity-skills/detecting-pass-the-ticket-attacks --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by mukul975Detecting 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
requestslibrary
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.
Frequently asked questions about Detecting Pass-the-Ticket Attacks
Similar skills
Asset Criticality Scoring for Vulns
Prioritize vulnerabilities based on asset criticality.
Performing Alert Triage with Elastic SIEM
Streamline alert triage processes in Elastic Security.
Active Directory Vulnerability Assessment
Secure your Active Directory with comprehensive assessments.
Active Directory Investigation
Streamline your Active Directory compromise investigations.
Parsing Artifacts with Eric Zimmerman Tools
Efficiently parse Windows forensic artifacts for analysis.
Operationalizing MISP Threat Feeds
Enhance threat detection with curated MISP feeds.
