CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse/SKILL.md·查看原始 Markdown·索引

name: competition-ad-certificate-abuse description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AD CS, certificate templates, enrollment rights, EKUs, SAN controls, PKINIT, certificate mapping, and cert-based privilege paths. Use when the user asks about ESC-style abuse, certificate templates, enrollment agents, EKUs, SAN or subject controls, smartcard or PKINIT logon, CA policy, or how an issued cert turns into accepted privilege. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.


Competition AD Certificate Abuse

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 identity edge is certificate-based and the hard part is proving how a template or CA policy turns into accepted privilege.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Identify the CA, template, enrolling principal, and accepting service before diving into every certificate detail.
  2. Separate template enrollability from cert-based authentication or privilege acceptance.
  3. Record EKUs, subject or SAN controls, issuance requirements, enrollment rights, and mapping behavior in compact blocks.
  4. Tie the issued cert to one accepted path: PKINIT, Schannel, LDAPS, WinRM, or another mapped service.
  5. Reproduce the smallest certificate issuance-to-acceptance chain that yields the decisive privilege.

Workflow

1. Map CA And Template Trust

2. Prove Cert-To-Privilege Acceptance

3. Reduce To The Decisive Abuse Chain

Read This Reference

What To Preserve