Skip to content

Active Directory

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

Active Directory attack techniques for red team engagements; golden tickets, skeleton keys, DCShadow, and related AD abuse primitives. Source: Pentest Laboratories (pentestlab.blog).

Purpose: This checklist covers post-compromise abuse of Active Directory's trust model itself - not initial access, but what happens once an attacker (or tester) already has a foothold in the domain and wants to escalate, persist, or move covertly using AD's own mechanisms against it. Every item here targets a structural weakness in how Kerberos, LDAP, or domain replication work by design, not a missing patch.

Function: Each entry maps to a specific abuse of a legitimate AD feature: golden/skeleton-key tickets abuse Kerberos trust in the KRBTGT account, DCShadow abuses domain replication to write directly to AD without touching event logs on a real DC, SPN discovery and Kerberoasting abuse how service accounts request tickets, and hash dumping abuses how domain credentials are stored and synced. None of these are "exploits" in the CVE sense - they're all abuse of intended functionality, which is exactly why they're hard to patch and easy to miss in a rushed assessment.

Goal: Establish whether an attacker who compromises a single domain-joined host or low-privileged account can escalate to Domain Admin, and - separately - whether they can then persist that access in a way that survives password resets, account disablement, or even a partial incident response. The golden ticket / skeleton key items specifically test the second question: can compromise become unkillable without a full KRBTGT rotation.

When & How to use this: Run this checklist during any internal or AD-focused engagement, ordered roughly as written - SPN discovery and Kerberoasting first (low-noise, credential-only), then DCShadow and ticket forgery only once you already hold DA-equivalent rights, since those require existing high privilege to execute in the first place. This checklist assumes you're already past initial access; pair it with Domain Escalation for the privilege-escalation path into DA, and Domain Persistence for the broader persistence toolkit beyond just tickets.

๐Ÿ“– Full deep-dive with detection/defense guidance: Tradecraft/active-directory.md

๐Ÿ“„ PDF references: AD_Attacks_.pdf ยท AD_Post_Exploitation.pdf

๐Ÿ› ๏ธ Related scripts: Scripts/PowerShell/ (adlogin.ps1, smblogin.ps1)



๐Ÿ“– Use These Checklists Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ Authorized testing only: confirm authority and scope before active testing. โš ๏ธ

โš ๏ธ Legal consequences depend on the conduct and applicable law; see 18 U.S.C. ยง1030 and DOJ CFAA charging policy. โš ๏ธ

โš ๏ธ For systems you do not own or administer, confirm authorization in advance and document scope in writing where policy, law, or contract requires it. โš ๏ธ

โญ Star this repo if you find it useful! โญ

## Related Files - [README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Checklists) - Checklists section index

๐Ÿ“„ Source: Checklists/ActiveDirectory.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Checklists

Clone this wiki locally