competition-lsass-ticket-materiallisted

# Competition LSASS Ticket Material 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 decisive host artifact lives in LSASS, ticket caches, or adjacent credential material and the hard part is proving what is replayable. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Separate raw credential material from actually usable replay edges. 2. Record logon session, LUID, ticket cache, package, account, and target service before broad conclusions. 3. Keep host artifact, extracted secret, replay attempt, and resulting acceptance in one chain. 4. Distinguish password, hash, ticket, DPAPI secret, SSP residue, and token by where each can actually be used. 5. Reproduce the smallest host-artifact-to-accepted-privilege path that proves the decisive edge. ## Workflow ### 1. Map LSASS And Adjacent Credential State - Record logon sessions, LUIDs, ticket caches, package names, SSPs, DPAPI context, and any service-account material tied to the active path. - Note whether the decisive value is a TGT, service ticket, delegated ticket, DPAPI secret, plaintext, hash, or package-specific secret. - Keep host source, account context, and cache location tied together. ### 2. Prove Replay Or Acceptance - Show where the ext