> For the complete documentation index, see [llms.txt](https://blog.r00t-hunter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.r00t-hunter.com/ad-lab-built-with-purpose/architecture-overview.md).
# Architecture Overview
#### Physical Hosts
| Host | Hardware | Hypervisor | Management IP |
| ----- | ------------------------------------- | -------------- | ------------- |
| SYS-1 | Intel i5 / 4 GB RAM / 250 GB Storage | Proxmox VE 8.x | 10.0.0.11 |
| SYS-2 | Intel i7 / 10 GB RAM / 500 GB Storage | Proxmox VE 8.x | 10.0.0.12 |
#### Network Segments
| Bridge | Network | Subnet | Purpose |
| ------ | ---------- | ------------ | ----------------------------------- |
| vmbr0 | WAN | External | Internet / WAN connectivity |
| vmbr1 | USA LAN | 10.10.0.0/24 | USA corporate environment |
| vmbr2 | India LAN | 10.20.0.0/24 | India corporate environment |
| vmbr3 | Management | 10.0.0.0/24 | Security and administration network |
#### Central Router
| Device | Version | Function |
| ------- | ------- | ------------------------------------------------------- |
| pfSense | CE 2.7 | Routing, Firewalling, OpenVPN Site-to-Site Connectivity |
#### Active Directory Forests
| Forest | Subnet | Relationship |
| ---------------- | ------------ | ------------- |
| usa.corp.local | 10.10.0.0/24 | Two-way trust |
| india.corp.local | 10.20.0.0/24 | Two-way trust |
#### USA Domain Infrastructure
| Hostname | IP Address | Role |
| --------- | ----------- | --------------------------------------- |
| DC-USA | 10.10.0.10 | Active Directory Domain Controller, DNS |
| FILE-USA | 10.10.0.20 | Samba File Server (AD-Joined) |
| WEB-USA | 10.10.0.30 | Apache Intranet Server |
| MAIL-USA | 10.10.0.40 | Postfix Mail Relay |
| WS-USA-01 | 10.10.0.101 | HR Workstation |
| WS-USA-02 | 10.10.0.102 | Finance Workstation |
| WS-USA-03 | 10.10.0.103 | IT Workstation |
| WS-USA-04 | 10.10.0.104 | DevOps Workstation |
#### India Domain Infrastructure
| Hostname | IP Address | Role |
| --------- | ----------- | --------------------------------------- |
| DC-INDIA | 10.20.0.10 | Active Directory Domain Controller, DNS |
| FILE-IND | 10.20.0.20 | Samba File Server (AD-Joined) |
| WEB-IND | 10.20.0.30 | Apache Intranet Server |
| MAIL-IND | 10.20.0.40 | Postfix Mail Relay |
| WS-IND-01 | 10.20.0.101 | HR Workstation |
| WS-IND-02 | 10.20.0.102 | Finance Workstation |
| WS-IND-03 | 10.20.0.103 | IT Workstation |
| WS-IND-04 | 10.20.0.104 | DevOps Workstation |
#### Management Network
| Hostname | IP Address | Role |
| --------- | ---------- | ---------------------------------------- |
| SEC-ONION | 10.0.0.50 | Detection Platform (Zeek, Wazuh, Kibana) |
| KALI-01 | 10.0.0.99 | Attack Platform / Red Team Workstation |
#### High-Level Topology Summary
| Segment | Systems |
| ----------------------- | ------------------------------------------------------- |
| USA Corporate Network | DC-USA, FILE-USA, WEB-USA, MAIL-USA, WS-USA-01–04 |
| India Corporate Network | DC-INDIA, FILE-IND, WEB-IND, MAIL-IND, WS-IND-01–04 |
| Management Network | pfSense, Security Onion, Kali Linux, Proxmox Hosts |
| Connectivity | OpenVPN Site-to-Site + Two-Way AD Trust Between Forests |
**An honest note on Samba vs Windows file servers:** FILE-USA and FILE-IND are Ubuntu 22.04 LXC containers running Samba joined to AD. This saves approximately 3 GB RAM a meaningful constraint-driven decision. The trade-off is real: Samba's SMB behavior, ACL edge cases, audit event format, and telemetry differ from a native Windows file server. Any detection work involving SMB telemetry from these hosts should be understood in that context. If you have the RAM budget for Windows file servers, use them.
**On Apache and Postfix:** These exist to support the phishing delivery scenario and provide intranet surface for BloodHound to graph. They are not deeply integrated into the attack chain. A simpler lab could omit them without losing much.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://blog.r00t-hunter.com/ad-lab-built-with-purpose/architecture-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.