🛠️ Active Directory Lab Project

🚧 Work in Progress 🚧
This project page is actively being updated as I build out my lab environment and document my experience.
I plan on adding these too in future updates:

[ Initial Hopes and Dreams ]

This project is more about setting up a playground for me to get some hands-on experience with Active Directory.
I’ve had some lab work involving Active Directory through my CompTIA Network+ course (TestOut — offered through my community college), where they provided virtual environments of a fully deployed AD setup.

I also gained lab experience from the course Workshop: Intro to Active Directory with Dale Hobbs offered by Antisyphon Training.
That course gave me a solid overview of central AD components, along with hands-on practice through a variety of labs. It was the biggest contributor to my desire to build my own lab space.

My main goal here is to deploy Active Directory in my home network and then create an environment I can both harden and test — giving myself perspectives from both offensive and defensive angles on how AD can be locked down.

[ Jul. 11, 2025 ]

📅 Initial Environment Setup

Things Done:
  • Created the initial Windows Server VM and Kali Linux VM.
  • Established network communication between the two VMs.
  • Installed Active Directory Domain Services (AD DS) and promoted Windows Server to a domain controller.
  • Confirmed DHCP allocation working via libvirt virtual network (NAT mode).
  • Configured DNS and network settings to allow basic connectivity across VMs.
Things To Do:
  • Verify DNS and name resolution from Kali to Windows Server.
  • Begin Active Directory Domain Services (AD DS) setup.
  • Decide on naming conventions for domains, users, and devices before scaling.
My Commentary:
- None. Straightforward actions and I am satisfied with progress.

[ Jul. 12, 2025 ]

📅 Active Directory and User Structure

Things Done:
  • Added Kali Linux as a BYOD-like client with a corresponding AD user Kal Eye.
  • Created a new Windows workstation VM HR-0002-win and contextual workstations/OUs (HR-0001-win & HR-0003-win).
  • Registered two users: Trevor Ross and Nicole Jule, both assigned to use HR-0002-win.
  • Created a logical OU structure in ADUC for users, departments, and devices (simulating HR department).
Things To Do:
  • Set up hMailServer to handle internal email for AD users.
  • Connect email clients (Outlook, Thunderbird) to test internal mail flow.
  • Begin simulating corporate communication workflows between users.
  • Explore AD group and OU usage for dynamic management of users and devices.
My Commentary:
- None. Straightforward actions and I am satisfied with progress.

[ Jul. 14, 2025 ]

📅 Mail Server, Shared Mailboxes, and SIEM Planning

Things Done:
  • Successfully configured hMailServer on Windows Server.
  • Installed and configured Thunderbird for mailbox access via IMAP.
  • Created a shared HR mailbox and a noreply@strange.local account.
  • Added an auto-delete rule for the noreply inbox and configured a reply message.
  • Built an internal distribution list manually in hMail (users@strange.local).
  • Began planning SIEM deployment using Wazuh.
  • Downloaded Docker — encountered "WSL version too old" error using WSL backend.
  • Troubleshot WSL on win-server (unsuccessfully). May require Docker reinstall.
Things To Do:
  • Improve the noreply rule to prevent replies from bypassing deletion.
  • Automate distribution list updates by syncing with an AD group or OU.
  • Configure Thunderbird for multiple mailbox access for HR users.
  • Begin Wazuh deployment using Docker on win-server (if feasible).
  • Tune SIEM agents to monitor key events on DC, workstations, and Kali VM.
My Commentary:
- Troubleshooting Windows Server was a nightmare; I may need another solution.
- The extra emails/groups make the experience feel more immersive.
- I’ll shift focus to security controls first instead of tinkering with mail setup.
- I’ll refine the organization later — security config best practices come first.

[ Jul. 18, 2025 ]

📅 Mac Setup & Network Connection

Things Done:
  • Failed repeatedly to get Wazuh on Windows Server VM.
  • Shifted Wazuh deployment to my Mac as a networked device.
  • Installed VirtualBox on the Mac and booted the Wazuh OVA.
  • Successfully started Wazuh on the Mac.
Things To Do:
  • Complete Wazuh setup and install an agent on the host machine.
  • Design network segmentation or VPN to optimize lab architecture.
  • Align with production settings for DCs, policies, and OUs — even on a small scale.
My Commentary:
- Wasted too much time trying Wazuh on win-server.
- I want a stable AD environment that mirrors production logic.
- Once stable, I’ll layer in security controls and maybe even run some attack simulations.