competition-windows-pivotlisted

# Competition Windows Pivot Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the challenge path is dominated by host-to-host movement, replayable ticket material, or Windows privilege edges. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Compress the pivot into a concrete chain: foothold -> recovered artifact -> replay path -> pivot host -> resulting capability. 2. Separate stored credential material from usable privilege. 3. Keep host evidence, ticket evidence, and privilege effect on one timeline. 4. Record the exact accepting service or host for every replayed artifact. 5. Reproduce the smallest pivot that still proves the privilege edge. ## Workflow ### 1. Recover The Replay Material - Inspect SAM, SECURITY, SYSTEM, NTDS, DPAPI, LSA secrets, browser stores, PowerShell history, ETW, Sysmon, and event logs in the active path. - Distinguish password, hash, ticket, cookie, vault blob, or gMSA material by where it can actually be used. ### 2. Trace The Pivot Chain - Map the protocol actually used: WinRM, SMB, RDP, WMI, admin shares, remote registry, or service control. - When Kerberos matters, record SPN, delegation, PAC or group data, encryption type, and the accepting service. - When AD edges ma