competition-identity-windows

Analyzes Active Directory, Kerberos, and Windows host evidence for CTF identity challenges.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-identity-windows-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-identity-windows
Source: https://github.com/dbx0/skills/tree/main/skills/identity-access/credential-access/competition-identity-windows
Command: npx skills add https://github.com/dbx0/skills --skill competition-identity-windows-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CTF challenges involving Active Directory, Kerberos tickets, Windows host artifacts, and enterprise mail often drown solvers in disconnected evidence. This Skill provides a structured methodology to trace identity flows, correlate host and mail evidence on one timeline, and prove lateral-movement chains instead of guessing at privilege. ## Core Features & Use Cases - Identity and AD Tracing: Maps principal origin, ticket minting, claims transformation, delegation modes, and the service that actually accepts a credential. - Windows Host Pivot Analysis: Correlates SAM, NTDS, DPAPI, LSA secrets, Sysmon, WMI, WinRM, SMB, and RDP artifacts into a single pivot graph with a concrete foothold-to-privilege chain. - Enterprise Messaging Correlation: Ties phishing lures, consent logs, mailbox rules, and identity-provider events together so mail paths and privilege paths stay connected. - Use Case: During a CTF, you recover a Kerberos ticket from a compromised host. Use this Skill to record the ticket type, SPN, and delegation mode, then reproduce the exact replay path to the pivot host that accepts it. ## Quick Start Ask the assistant to trace the Kerberos ticket and lateral-movement chain across the sandbox hosts after the ctf-sandbox-orchestrator has established the scenario.

Frequently Asked Questions about competition-identity-windows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a Kerberos ticket in a CTF challenge?

Record the ticket type, SPN, delegation mode, PAC or group data, encryption type, and cache location, then identify the service that accepts it. This Skill walks through principal origin, ticket minting, and the final accepting service as one chain.

How to correlate Windows host artifacts for lateral movement analysis?

Treat SAM, SECURITY, SYSTEM, NTDS, DPAPI, LSA secrets, Sysmon, WMI, WinRM, SMB, and RDP as one pivot graph. Express movement as a concrete chain: foothold, recovered artifact, replay path, pivot host, and resulting capability.

When should I use this skill instead of other CTF identity skills?

Use it for general identity-flow and Windows host evidence challenges after the sandbox orchestrator is active. For narrow topics like AD CS abuse, DPAPI chains, LSASS material, OAuth flows, or relay coercion, it routes you to the dedicated specialization skill.

Does possessing a hash or ticket prove domain compromise?

No. The skill explicitly separates credential possession from accepted privilege. You must reproduce the privilege edge with a reproducible edge-by-edge chain showing which service accepts the credential or ticket.

What evidence should be preserved during a Windows identity CTF?

Keep compact blocks for SIDs, SPNs, ticket fields, event IDs, logon IDs, and mailbox rules, plus a separate block for host pivots and replayed artifacts. Store raw artifacts, parsed summaries, and derived timelines as separate outputs.