competition-identity-windows

Trace identity flows, tickets, and Windows host artifacts across sandbox-linked nodes.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-identity-windows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-identity-windows
Source: https://github.com/xjtu-wang/DigAgent/tree/main/.agents/skills/competition-identity-windows
Command: npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-identity-windows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps security analysts trace identity flows, tickets, and Windows host artifacts within a sandboxed environment, linking credential material and lateral-movement chains to provide reproducible investigations.

Core Features & Use Cases

  • Trace principal origin, sync path, token or ticket minting, claims transformation, group resolution, and accepting service in Active Directory and Kerberos contexts.
  • Correlate Windows host artifacts (SAM, SECURITY, SYSTEM, NTDS, DPAPI, LSA secrets) with enterprise messaging events (mailbox rules, consent logs) to build end-to-end pivot chains.
  • Reproduce pivot chains across sandbox-linked nodes by documenting the edge-by-edge sequence from foothold to privilege elevation.
  • Preserve exact evidence blocks: SIDs, SPNs, ticket fields, event IDs, mailbox-rule changes, and pivot hosts for consistent timelines.

Quick Start

Map the identity chain and correlate host and mailbox evidence to reproduce the access path.

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 Kerberos ticket flows and Active Directory lateral movement?

Trace Kerberos ticket flows and Active Directory lateral movement by mapping principal origin, token minting, and group resolution to reveal credential paths. Documenting SIDs, SPNs, and ticket fields provides reproducible timelines for investigations.

Can I correlate Windows host artifacts with mailbox rules to map pivot chains?

Correlate Windows host artifacts like SAM, SECURITY, and NTDS with mailbox rules and consent logs to build end-to-end pivot chains. Linking credential material across sandbox-linked nodes reproduces the edge-by-edge sequence from foothold to privilege elevation.

What is the best way to document SIDs and SPNs during identity forensics?

Document SIDs and SPNs during identity forensics by preserving exact evidence blocks alongside Windows event IDs. This approach maintains consistent timelines and captures the edge-by-edge pivot sequences needed for reproducible investigations.

Do I need a sandbox environment to reproduce Windows credential pivot chains?

A sandboxed environment is required to reproduce Windows credential pivot chains and map identity evidence across linked nodes. It satisfies requirements for documenting ticket fields, event IDs, and mailbox-rule changes within controlled assumptions.

Why does mapping Active Directory privilege escalation require tracking DPAPI and LSA secrets?

Mapping Active Directory privilege escalation requires tracking DPAPI and LSA secrets because they contain the credential material used for lateral movement. Correlating these host artifacts with Kerberos tickets reveals how privileges are gained across nodes.