> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/active-directory.md). # Active Directory Active Directory pentesting methodology for domain enumeration, Kerberos attacks, ACL abuse, credential extraction, token abuse, and lateral movement. Practical Active Directory notes for offensive security labs and internal penetration testing: discovery, domain mapping, Kerberos, credentials, ACLs, BloodHound paths, and lateral movement. ## Active Directory Workflow 1. Build domain context: domain name, domain controllers, users, groups, computers, OUs, GPOs, and trusts. 2. Enumerate accessible shares, sessions, local admin rights, LDAP objects, and BloodHound relationships. 3. Check Kerberos attack paths such as user enumeration, AS-REP Roasting, Kerberoasting, and password spraying. 4. Review ACLs, dangerous permissions, ownership, DACL/SACL/ACE entries, and DCSync rights. 5. Extract or validate credentials through LSASS, SAM, MSCache, tokens, hashes, and tickets. 6. Convert findings into lateral movement paths using WinRM, SMB, Kerberos tickets, token abuse, or hash reuse. ## Active Directory Techniques

:book-open:

Fundamentals

Active Directory security notes for Active Directory Fundamentals, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.Active Directory Fundamentals

:flask:

Lab Setup

Active Directory security notes for Active Directory Lab, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.Active Directory Lab

:magnifying-glass:

Enumeration

Active Directory enumeration workflows for users, groups, computers, GPOs, shares, ACLs, domain controllers, BloodHound, PowerView, LDAP, and Impacket.Active Directory Enumeration

:shield-halved:

ACL and Permissions

Active Directory ACL abuse notes covering security descriptors, DACL, SACL, ACE, dangerous rights, BloodHound paths, DCSync, and password spraying.ACL and Permission Abuse

:ticket:

Kerberos

Kerberos attack notes for Active Directory covering AS-REP Roasting, Kerberoasting, password spraying, Rubeus, Impacket, SPNs, tickets, and Wireshark analysis.Kerberos Attacks

:key:

Credentials and Tokens

Windows and Active Directory credential notes covering LSASS, SAM, MSCache, access tokens, impersonation tokens, LogonSessions, registry hives, and Mimikatz.Credentials and Tokens

:right-left:

Lateral Movement

Active Directory lateral movement notes covering Pass-the-Hash, Pass-the-Ticket, Overpass-the-Hash, token impersonation, NTLM roasting, LLMNR poisoning, and Kerberos tickets.Lateral Movement
\## Recommended Tools * [BloodHound](/active-directory/enumeration/bloodhound-analysis.md) and SharpHound for relationship mapping and attack path analysis. * [PowerView](/active-directory/enumeration/powerview.md) for PowerShell-based domain enumeration. * [Impacket and rpcclient](/active-directory/enumeration/impacket-and-rpcclient.md) for Linux-based domain enumeration and abuse. * [Rubeus](/active-directory/kerberos/rubeus-installation.md) for Kerberos ticket operations from Windows. * [ldapsearch](/active-directory/enumeration/ldapsearch.md), Pywerview, and JXplorer for LDAP object discovery. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/active-directory.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.