<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lab on SirZak</title><link>https://sirzak.rocks/tags/lab/</link><description>Recent content in Lab on SirZak</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 SirZak</copyright><lastBuildDate>Mon, 10 Aug 2026 11:00:00 -0500</lastBuildDate><atom:link href="https://sirzak.rocks/tags/lab/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an Active Directory attack range</title><link>https://sirzak.rocks/homelab/ad-attack-range/</link><pubDate>Mon, 10 Aug 2026 11:00:00 -0500</pubDate><guid>https://sirzak.rocks/homelab/ad-attack-range/</guid><description>&lt;h2 class="relative group"&gt;What I built
 &lt;div id="what-i-built" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-i-built" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;A self-contained Active Directory forest that exists purely to be attacked: a
Windows Server domain controller, a member server, and a Windows workstation, all
on an isolated VLAN with no route to anything I care about. Every technique I read
about in a writeup, I can actually run here first.&lt;/p&gt;</description></item></channel></rss>