competition-ad-certificate-abuse

1# Competition AD Certificate Abuse
2 
3Use 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.
4 
5Use 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.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Identify the CA, template, enrolling principal, and accepting service before diving into every certificate detail.
122. Separate template enrollability from cert-based authentication or privilege acceptance.
133. Record EKUs, subject or SAN controls, issuance requirements, enrollment rights, and mapping behavior in compact blocks.
144. Tie the issued cert to one accepted path: PKINIT, Schannel, LDAPS, WinRM, or another mapped service.
155. Reproduce the smallest certificate issuance-to-acceptance chain that yields the decisive privilege.
16 
17## Workflow
18 
19### 1. Map CA And Template Trust
20 
21- Record CA configuration, template name, enrollment permissions, manager approval, authorized signatures, EKUs, subject requirements, and SAN behavior.
22- Note whether the path depends on alternate subject names, `UPN`, DNS names, enrollment agent behavior, or template supersedence.
23- Keep principal, template, and issuance policy tied together.
24…