This article is Day 23 of a 100-day ethical hacking course, introducing Active Directory fundamentals as the foundation for enterprise penetration testing. It covers AD architecture (forests, domains, OUs), Kerberos authentication mechanisms and their exploitable weaknesses, the standardized five-step attack chain from initial access to domain compromise, and practical setup of a free lab environment using Windows Server evaluation software. The article matters because approximately 90% of Fortune 500 companies run Active Directory, making AD compromise skills essential for professional penetration testers and representing the single most valuable attack surface in enterprise environments.
- Active Directory as single point of failureEvery resource in an AD domain (file servers, applications, printers) trusts the Domain Controller to verify identity and grant access. Compromising the Domain Controller compromises everything in the domain because the entire centralised trust model collapses—this is why Domain Admin access represents total domain compromise including every user credential, server, file share, and application.
- Five-step methodical attack chainThe article defines AD compromise as a structured progression: initial access to a workstation, local privilege escalation to admin on that machine, credential harvesting from that machine, lateral movement to a machine with a Domain Admin logged in, and finally capturing or escalating to Domain Admin. This chain provides the logical framework for all subsequent Days 24-31 techniques and distinguishes systematic red team operators from those randomly trying attacks.
- Kerberos design weaknesses enable ticket attacksKerberos uses three-step encrypted ticket exchange (AS-REQ/AS-REP for TGT, TGS-REQ/TGS-REP for service tickets, AP-REQ/AP-REP for application access) but has critical exploitable assumptions: the KDC is always trusted and tickets are time-bounded but not session-bounded. This allows AS-REP Roasting (Step 1), Kerberoasting (Step 2), Pass the Ticket (Step 3), and Golden Ticket forgery—with forged tickets remaining valid for 10 years by default.
- FSMO roles concentrate high-value targetsFive Flexible Single Master Operation roles exist per forest and domain with domain-wide compromise consequences: Schema Master (controls AD schema changes), Domain Naming Master (manages domain additions), RID Master (allocates SID pools), PDC Emulator (time sync and lockout management), and Infrastructure Master (cross-domain references). The article emphasizes these servers are high-impact red team targets beyond standard Domain Admin.
- Tier 1 attack surface requires systematic enumerationThe article prioritizes immediate targets: service accounts with SPNs for Kerberoasting, accounts without pre-auth for AS-REP Roasting, unconstrained delegation hosts, LLMNR/NBT-NS enabled networks, and NTLM authentication for Pass the Hash. Professional engagement methodology uses this list within the five-step chain rather than randomly testing—distinguishing systematic assessments from vulnerability scanner output.
- Free lab setup uses Windows Server evaluation softwareThe article provides exact step-by-step PowerShell commands to promote Windows Server 2022 evaluation (180-day free license) to a domain controller, create lab users with realistic passwords, and register an SPN on a service account for Kerberoasting practice. Total cost is zero using VirtualBox, Windows Server eval, Windows 10 eval, and Kali Linux on isolated host-only networking.
- First enumeration commands reveal attack surfaceThe article demonstrates enum4linux returns domain shares (ADMIN$, C$, NETLOGON, SYSVOL), domain SID, and user list in one command; ldapsearch performs anonymous LDAP queries; crackmapexec queries password policy lockout thresholds; and GetUserSPNs.py identifies Kerberoastable service accounts. These five-minute enumeration steps produce reconnaissance output identical to real penetration test reports.
- Password policy query prevents account lockoutsThe article emphasizes querying password policy before password spraying is critically important because it reveals the lockout threshold—exceeding this limit disables accounts domain-wide, making this reconnaissance step mandatory to prevent disrupting the entire domain during testing and distinguishing professional from careless testing.
Bottom line: Active Directory compromise follows a consistent five-step chain (initial access → local escalation → credential harvesting → lateral movement → domain compromise) rather than single exploits, and understanding Kerberos ticket weaknesses combined with systematic enumeration of the three-tier attack surface provides the foundation for achieving Domain Admin access in enterprise environments. Building a free lab using Windows Server evaluation software and running basic enumeration commands (enum4
🛡️ ETHICAL HACKING COURSE
FREE
Part of the 100-Day Free Ethical Hacking Course — from complete beginner to professional penetration tester
⏱️ 28 min read · 3 hands-on exercises
📊 How familiar are you with Windows Active Directory environments?
📋 What You’ll Master in Day 23 — Active Directory Basics
- What Is Active Directory and Why Every Enterprise Runs It
- Forest, Domain, OU — The AD Object Hierarchy Explained
- Kerberos Authentication — How It Works and Where It Breaks
- The AD Attack Surface — What Ethical Hackers Target First
- Building Your Free AD Lab — Complete Step-by-Step Setup
- First LDAP and SMB Enumeration Commands from Kali
- Frequently Asked Questions
On Day 22 we covered exploitation techniques beyond Metasploit — manual methods that work when automated frameworks fail. Today we step into the territory that most enterprise penetration testing engagements are fundamentally about: Windows Active Directory environments. The next eight days of this course cover AD exclusively, from structure today through to domain compromise by Day 30.
This is Day 23 of the 100-Day Free Ethical Hacking Course. Everything you have learned so far — Linux commands, networking, web application vulnerabilities, exploitation techniques — feeds directly into what comes next. AD is where all those skills converge into real enterprise-level penetration testing.
What Is Active Directory and Why Every Enterprise Runs It
Active Directory (AD) is Microsoft’s centralised directory service — a system for managing users, computers, groups, policies, and resources across an entire Windows network from a single point of control. Introduced with Windows 2000 Server, it has been the backbone of enterprise IT infrastructure for over two decades. As of 2026, approximately 90% of organisations with more than 100 employees use Active Directory as their primary identity and access management platform.
Active Directory works on a single fundamental principle: every resource in the domain — whether it is a file server, a web application, or a printer — trusts the Domain Controller to verify who a user is and what they are allowed to access. This centralised trust model is enormously efficient for IT administration, but from a security perspective it creates a single point of total failure. Compromise the Domain Controller, and you compromise everything.
DC01 · DC02 · RID Master · PDC Emulator
DC03 · Development environment
⏱️ Time: 2 minutes · No tools required
Before reading the rest of this guide, write down the five logical steps needed to go from “low-privileged user on a workstation” to “Domain Admin of the entire domain.” Think about what information and access you need at each step.
Step 2: Local privilege escalation → How do you become local admin on that machine?
Step 3: Credential harvesting → How do you get domain credentials from that machine?
Step 4: Lateral movement → How do you reach a machine where a DA is logged in?
Step 5: Domain compromise → How do you capture or escalate to Domain Admin?
This is the AD attack chain. Every technique in Days 24–31 maps to one of these five steps. Knowing where you are in the chain tells you exactly what you need to do next — this is how real red team operators think.
📸 Draw your attack chain (even on paper) and share a photo in your notes.
🧠 QUICK CHECK — Section 1
Forest, Domain, OU — The AD Object Hierarchy Explained
Active Directory uses a strict four-level hierarchy: Forest → Domain → Organisational Unit (OU) → Objects. Understanding this hierarchy tells you where high-value targets live, which trust boundaries exist, and which attacks are possible at each level.
The Hierarchy From Top to Bottom
The key objects inside a domain that matter most for penetration testing are: User accounts (regular users and service accounts), Computer accounts (workstations and servers), Security Groups (especially Domain Admins, Enterprise Admins, Schema Admins), and Group Policy Objects (GPOs) that control security settings across all domain-joined machines.
FSMO Roles — Five Special Domain Controllers Every Red Teamer Knows
Every AD forest and domain assigns exactly five Flexible Single Master Operation (FSMO) roles to specific domain controllers. These roles matter to ethical hackers because the servers that hold them are high-impact targets whose compromise has domain-wide consequences beyond standard Domain Admin.
Kerberos Authentication — How It Works and Where It Breaks
Kerberos is the primary authentication protocol in Active Directory, replacing NTLM for most domain authentication. Understanding how it works at the ticket level is mandatory for AD hacking — every major AD attack technique from Day 24 onwards exploits a specific weakness in Kerberos design or configuration.
The critical design insight is this: Kerberos assumes the KDC is always trusted and tickets are time-bounded but not session-bounded. An attacker who can steal or forge a Kerberos ticket can authenticate as any user — including Domain Admin — without knowing that user’s password. A Golden Ticket forged from the krbtgt hash remains valid for 10 years by default. This is why these techniques form the core of the most impactful AD attacks you will learn in Days 25 and 26.
🧠 QUICK CHECK — Section 3
The AD Attack Surface — What Ethical Hackers Target First
A standard enterprise AD environment presents dozens of potential misconfigurations and attack surfaces. Knowing how to enumerate these systematically is what separates a professional assessment from a list of CVEs from a vulnerability scanner. The list below is the standard priority order that experienced red teamers follow in every AD engagement.
Building Your Free AD Lab — Complete Step-by-Step Setup
Every technique from Day 24 onwards requires a working Active Directory lab. The good news is that you can build a fully functional AD environment for zero cost using Microsoft’s evaluation software. Here is the exact setup I recommend for every student taking this course.
What You Need
Step-by-Step Domain Controller Setup
⏱️ Time: 20–30 minutes · Target: TryHackMe (authorised platform)
If your home lab is not set up yet, use TryHackMe’s free Active Directory Basics room to explore a real AD environment in your browser without installing anything locally.
Steps:
1. Create a free TryHackMe account if you do not have one
2. Join the “Active Directory Basics” room
3. Deploy the machine and connect via TryHackMe’s browser-based AttackBox
4. Follow the room tasks — answer each question as you complete it
5. Note the AD structure, the OU layout, and the domain controller hostname
TryHackMe is an authorised learning platform. All testing happens within their controlled environment. This room complements today’s theory perfectly.
📸 Screenshot your completed TryHackMe room certificate and share it in your notes.
First LDAP and SMB Enumeration Commands from Kali
Once your AD lab is running and Kali Linux is on the same host-only network, you are ready to run your first real enumeration commands. These are the exact commands I run in the first ten minutes of every AD engagement. Understanding the output they produce is the foundation for every attack in Days 24–31.
⏱️ Time: 20–30 minutes · Target: Your lab DC (lab.local) on host-only network
With your AD lab running, execute the following complete enumeration sequence from Kali Linux. Document everything you find.
Document: How many users found? What shares are visible? Are there any SPNs (service accounts)? What is the password policy lockout threshold?
📸 Screenshot your enum4linux user list and share it in your notes. Tag #ethicalhackingday23
🧠 QUICK CHECK — Section 6
📋 Commands Used Today — Day 23 Reference
🏆 Mark Day 23 as Complete
You have entered enterprise territory. Lock in your progress.
❓ Frequently Asked Questions
What is Active Directory and why is it important for ethical hacking?
What is the difference between a forest and a domain?
How do ethical hackers enumerate Active Directory?
How do I build a free Active Directory lab at home?
What is Kerberos and why is it central to AD attacks?
What should I do after completing today’s lab setup?
Day 22: Exploitation Beyond Metasploit
Day 24: Active Directory Attacks
📚 Further Reading
- Day 22: Exploitation Beyond Metasploit — The manual exploitation skills from Day 22 are directly applied in AD attacks — especially when automated tools like Metasploit are blocked by EDR solutions.
- Day 21: Metasploit Framework — Metasploit’s post-exploitation modules are heavily used for AD credential harvesting and lateral movement in Days 25–30.
- Ethical Hacking: Enumeration Hub — The complete category covering all enumeration techniques — LDAP, SMB, RPC, Kerberos — that feed into the AD attack chain.
- Microsoft: Active Directory Domain Services Overview — The authoritative Microsoft documentation on AD architecture, FSMO roles, and forest/domain structure for defenders and testers alike.
- MITRE ATT&CK: Discovery Tactics — MITRE’s complete catalogue of discovery techniques used against Active Directory environments, mapped to real-world threat actor behaviour.

