> 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/why-i-built-it-this-way.md). # Why I Built It This Way Most publicly available AD labs teach a single-domain Kerberoast path with a flag at the end. That is useful for technique memory. It is not useful for understanding how authentication paths chain through AD trust relationships, or for building detection logic that correlates network-layer events against host-layer telemetry. The specific gaps this lab was built to address: * Inter-forest trust authentication paths and where SID filtering changes the outcome * DCSync detection from a non-DC account versus legitimate DC replication traffic * RC4 etype anomaly detection without generating false positives on legacy app traffic * Zeek `kerberos.log` and EventID 4769 correlation for Kerberoasting detection * AdminSDHolder ACL propagation timing and what EventID 5136 looks like for that * LSASS access detection via Sysmon EventID 10 across different access right masks The lab is configured with known privilege paths so those paths can be practiced and their detection surfaces verified. That is intentional this is a detection validation environment, not a chaos simulation or red team rehearsal. Real engagements have more dead ends, blocked pivots, stale credentials, WinRM certificate failures, and partially deployed MFA than any homelab will ever replicate. **Scope note:** All subnets are RFC 1918 private space. No traffic leaves the physical hosts. --- # 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/why-i-built-it-this-way.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.