detecting-pass-the-ticket-attacks▌
mukul975/Anthropic-Cybersecurity-Skills · updated May 25, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Detect Kerberos Pass-the-Ticket (PtT) attacks by analyzing Windows Event IDs 4768, 4769, and 4771 for anomalous ticket usage patterns in Splunk and Elastic SIEM
| name | detecting-pass-the-ticket-attacks |
| description | Detect Kerberos Pass-the-Ticket (PtT) attacks by analyzing Windows Event IDs 4768, 4769, and 4771 for anomalous ticket usage patterns in Splunk and Elastic SIEM |
| domain | cybersecurity |
| subdomain | threat-detection |
| tags | - kerberos - pass-the-ticket - active-directory - splunk - elastic - credential-theft - windows-security |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| d3fend_techniques | - Token Binding - Execution Isolation - Restore Access - Application Protocol Command Analysis - Process Termination |
| nist_csf | - DE.CM-01 - DE.AE-02 - DE.AE-06 - ID.RA-05 |
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
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.
How to use detecting-pass-the-ticket-attacks on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add detecting-pass-the-ticket-attacks
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches detecting-pass-the-ticket-attacks from GitHub repository mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate detecting-pass-the-ticket-attacks. Access the skill through slash commands (e.g., /detecting-pass-the-ticket-attacks) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★69 reviews- ★★★★★Kwame Jain· Dec 28, 2024
detecting-pass-the-ticket-attacks fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ren Li· Dec 24, 2024
We added detecting-pass-the-ticket-attacks from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Diego Okafor· Dec 24, 2024
Useful defaults in detecting-pass-the-ticket-attacks — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Camila Thomas· Dec 16, 2024
detecting-pass-the-ticket-attacks reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Isabella Perez· Dec 4, 2024
detecting-pass-the-ticket-attacks is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Noah Huang· Nov 27, 2024
detecting-pass-the-ticket-attacks reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Lucas Haddad· Nov 23, 2024
Registry listing for detecting-pass-the-ticket-attacks matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Luis Shah· Nov 23, 2024
detecting-pass-the-ticket-attacks fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Valentina Diallo· Nov 19, 2024
detecting-pass-the-ticket-attacks is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Luis Sharma· Nov 15, 2024
Keeps context tight: detecting-pass-the-ticket-attacks is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 69