agentleFS
noahfranklinnoahfranklin/gideon/skills/active-directory-pentest/SKILL.md

active-directory-pentest

Skill2 starsChanged 47 days agoMITView on GitHub

Use when testing an on-prem Active Directory environment — enumeration, Kerberos attacks (Kerberoasting, AS-REP roasting, delegation abuse), credential access (NTLM/hashes, LSASS, DCSync), ACL/permission abuse, GPO abuse, trust attacks, and domain-privilege-escalation attack paths. Maps to MITRE ATT&CK, with detection signals and remediation. Assumed-breach, authorized engagements only.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test for ESC1–ESC8 template/permission misconfigurations enabling privilege escalation via certificate abuse.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Active Directory Penetration Testing

Attack-path-driven assessment of on-prem AD (typically assumed-breach: you start with a low-priv foothold and work toward Domain Admin / specific objectives). Mapped to MITRE ATT&CK. Every technique lists its detection signal so defenders can catch it.

0. Authorization gate

  • Written scope: domain(s), foothold provided, objectives (DA / specific data).
  • DCSync / credential-dumping explicitly authorized (high impact).
  • Data-handling + cleanup (remove any created objects/accounts) agreed.

1. Enumeration (map the terrain)

  • Domain/forest structure, trusts, OUs, users, groups, computers, GPOs, ACLs.
  • Build the attack graph: who can reach Domain Admin via group membership, ACLs, sessions, or delegation. (BloodHound-style graph analysis is central — see vuln-chaining for path reasoning.)
  • Find high-value targets: DAs, service accounts, privileged sessions, unconstrained-delegation hosts.

2. Kerberos attacks

  • Kerberoasting: request service tickets for SPN accounts → offline crack weak service-account passwords. Detect: anomalous TGS requests / RC4.
  • AS-REP roasting: accounts without pre-auth → crackable. Detect: AS-REQ without pre-auth.
  • Delegation abuse: unconstrained (capture TGTs), constrained, and resource-based constrained delegation → impersonation. Detect: unusual S4U / TGT use.
  • Fix: strong/managed service-account passwords (gMSA), require pre-auth, remove/limit delegation, tier-0 isolation.

3. Credential access

  • NTLM hash capture (pair with network-pentest relay/poisoning), LSASS credential extraction (authorized), DPAPI, cached creds.
  • DCSync (replicate directory secrets) with sufficient rights → domain-wide compromise.
  • Fix: Credential Guard, LSASS protection, restrict replication rights, tiered admin model, LAPS for local admin passwords.

4. ACL, GPO & object abuse

  • Dangerous ACLs (GenericAll/WriteDACL/WriteOwner, force-change-password rights) create escalation edges.
  • GPO edit rights → code execution across linked OUs.
  • Fix: audit and tighten ACLs, restrict GPO edit rights, monitor privileged object changes.

5. Persistence & domain dominance (document, don't linger)

Golden/Silver ticket concepts, AdminSDHolder, DCShadow — understand for detection guidance; in engagements, prove capability and document rather than establishing lasting persistence.

  • Fix: krbtgt rotation (twice), tier-0 protection, monitoring of directory-level changes.

6. Trusts

  • Enumerate domain/forest trusts; assess cross-domain/forest escalation paths.
  • Fix: SID filtering, selective authentication, minimize trusts.

7. Tooling

BloodHound/SharpHound (attack graph), PowerView, impacket (secretsdump, GetUserSPNs, ntlmrelayx), Rubeus, certipy (AD CS — ESC1–ESC8). Follow RoE.

8. AD CS (certificate services)

Test for ESC1–ESC8 template/permission misconfigurations enabling privilege escalation via certificate abuse. Fix: harden certificate templates, restrict enrollment, monitor issuance.

9. Reporting & correlation

Present findings as attack paths, not isolated issues (foothold → step → step → DA), with the single highest-leverage fixes that break the most paths. Route path reasoning to vuln-chaining, priv-esc to privilege-escalation, cloud-identity to entra-cloud-pentest. Checklist: references/ad-checklist.md.


<sub>© 2026 noahfranklin · Part of the Gideon security suite · MIT License · Original work.</sub>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.