Repository navigation
Description
ADR-0029 sized the lab's Windows domain and gave it a namespace and a clock;
build-the-lab-domain.md is the
procedure. #265 closed on the decision and the runbook, and the build lost its
tracker — the roadmap still says "decided, not built", and two issues wait
behind it. This is the tracker.
What is decided
Six guests on Saruman, the .50 decade of ImaginationLAN: bahamut and
leviathan (domain controllers), titan and ramuh (members), carbuncle
and siren (endpoints). Servers continuous, endpoints per session. Namespace
ad.matrix.elysium / NetBIOS AD, clock from the gateway, DNS inward only,
domain scraped by the lab's Prometheus and never published. Hicks reaches it
by the rule ADR-0031 keeps open, and build-the-lab-domain.md §10 records
what a workstation then reaches on VLAN 30 — the list #228's narrowing waits
for.
What waits on it
- Run Wazuh on Saruman — the heaviest component in ADR-0007 #266 Wazuh and Run Velociraptor on Saruman #267 Velociraptor: ADR-0030 puts both in
stacks/soc/on a
second guest,odinat10.0.30.60, and both are agentless without this
domain — "an agentless Wazuh still has nothing to say". - ADR-0014's range: an attack VM pointed at an estate with no domain teaches
nothing (build-the-playground.md§0). - The three domain rules already live in
stacks/lab/prometheus/rules/lab.rules.yaml
with promtool tests, and the commented-outwindowsscrape job in the lab's
prometheus.yamlwaits to be uncommented once six machines answer — the
file says why it landed commented.
Order of work
The runbook's, §1 through §11, at Saruman from a Hicks workstation: create
the six VMs, install and address, promote bahamut with the clock set before
anything joins, the second DC, join the members and build the tiers, the
authentication generator, windows_exporter and the licence clock, turn on
the scrape, verify, record what Hicks now reaches, write it down. No purchase;
evenings.
stacks/soc/ can be authored and CI-validated before this is built — the
stacks/lab precedent — and then waits only on this.
Corrected 2026-09-19
A gate this issue did not name. ADR-0029's sizing — six guests, servers continuous, endpoints per session — rests on ~90 derived write IOPS that nobody has measured. #418 closed with the SSDs fitted and unassigned: no logical drive, no thin pool, alexander still on the HDD mirror, no fio. roadmap.md: "an unassigned drive changes no duty cycle either — the sentence above holds until the runbook's step 8 measures both arrays." That work is #527, and it precedes this.
Also worth settling before starting, because #448 raises it: whether this domain is built by hand from the runbook's eleven sections and later rebuilt from the pipeline, or built from the pipeline the first time. This issue stays the tracker either way; the order of work above assumes the first.
Corrected 2026-09-20
The gate named yesterday has cleared: #527 closed on 2026-09-20 — logical drive 2, both arrays measured at 4 KiB QD1 (the 7.2K mirror 741 IOPS, the SSD mirror 7,952), alexander moved to large_data and rebooted from flash. ADR-0029's sizing now rests on a measured number, and it is two orders of magnitude above the ~90 it assumed for the spindles. Nothing precedes this any more. The order of work above stands; the build-by-hand-then-rebuild question with #448 is still open and still this issue's to settle before starting.
Activity
Merge pull request #490 from Gerrrt/gerrrt/ifrit-purchase-range-build…
docs(runbooks): the Saruman SSD fit becomes a procedure, and the tray…
Gerrrt commentedon Sep 24, 2026
Decided 2026-09-23: by hand first, then rebuilt from the pipeline
This settles the question left open on 2026-09-19 and 2026-09-20. The domain is built by hand from
build-the-lab-domain.md§1–§11, and later rebuilt from #448's pipeline (with #440's templates and #445's provisioning).Why this order:
slmgr /dlvreadings run out, which is Build the lab's VM templates with Packer, so the domain's evaluation clock stops costing a day #440's reason to exist.Nothing precedes the build. #527 cleared the IOPS gate, and
Sarumanread today with about 109 GB of memory available, 48 threads, andlarge_dataat 8 % of 876 GiB. The two endpoints wait on the buy table's Windows 11 Pro keys; the four servers do not.🤖 Generated with Claude Code
Gerrrt commentedon Sep 26, 2026
2026-09-26: both Windows 11 Pro keys were bought on 2026-09-25 and are activated on
carbuncleandsiren. Their DHCP reservations (10.0.30.54/.55) are onmorpheus. The endpoints aren't joined yet, because the DCs aren't built. The roadmap buy table is now empty (#665).docs(hardware): Windows keys used, smaug's Exos reordered after refun…
fix(lab): reindent the scrape-section comment and drop the stale 'unc…
fix(secrets): the lab's secrets live in git, not only on alexander (#667
docs(lab): the single-file bind mount means edit-then-reload can be a…
feat(lab): turn on the windows scrape now the domain is built (#414) (#…
Gerrrt commentedon Sep 26, 2026
Built by hand 2026-09-24 to 2026-09-25 — steps 1–8 done, verified on the running domain
Built by hand from
build-the-lab-domain.md, the order decided on 2026-09-23 (by hand first, then #448 rebuilds). All six guests exist onSaruman, joined toad.matrix.elysium/ NetBIOSAD.The two endpoints used the two Windows 11 Pro keys (retail), which leave the buy table.
What was done (runbook §1–§8)
large_data(ssd=1),firewall=0per NIC, joined; DCs static, the other four onmorpheusDHCP reservations; DNS at the two DCs; IPv6/LLMNR/NetBIOS/WPAD left at defaults (§0's "do not harden").bahamutpromoted with the clock set from10.0.30.1before anything joined (it reads 5.5 ms offmorpheus);leviathanthe second DC; replication clean (repadmin /replsummary0 fails); root hints removed on both; each DC's own DNS set partner-first-then-loopback.Tier 0 Adminsin Domain Admins; the Tier 0 deny-logon GPO linked to Servers + Workstations (the control a violation becomes an event against);titanshares with a decoy. The exploitable contents (users, roastable/delegation weaknesses) are left to Give the lab domain users and deliberate weaknesses, one tag at a time #449 by design — nothing observes them yet.windows_exporterv0.31.8 on all six, firewalled toalexander(10.0.30.40); licence-clock task on the four servers.windowsscrape turned on; all sixup=1on the lab Prometheus. Clock check healthy:bahamut=NTP,leviathan=NT5DS, neither on Local CMOS.Repo caught up with reality
alexander) · docs(lab): the single-file bind mount means edit-then-reload can be a no-op #668 — the single-file bind-mount gotcha documented · docs(lab): correct build-the-lab-domain.md from the hand build (#414) #669 — eightbuild-the-lab-domain.mdcorrections from the run.alexander's checkout reconciled tomain(was 203 behind).What remains to close this
Flagged for a decision
secrets/lab.sops.yamlis encrypted to a single key held only onalexander(now in git, so the ciphertext survives a disk loss, but the key does not). Second recipient or off-box key backup — an ADR-0024-style call (fix(secrets): the lab's secrets live in git, not only on alexander #667).🤖 Generated with Claude Code
docs(lab): correct build-the-lab-domain.md from the hand build (#414) (…
Gerrrt commentedon Sep 26, 2026
2026-09-26: a dependency check. §6 needs one ordinary domain user for a 15-minute scheduled task (runbook §6), but it's recorded here as waiting on #449's population. #449 waits on this issue and on #448, which is the end of the automation chain (#440 → #445 → #448). As written, this issue can't close until milestone 5 is nearly done, and #449 waits on it: a cycle.
Two ways out. Make a single ordinary user by hand for §6's task now and leave #449 the population and the weakness tags. Or record §6 as deferred to #448's rebuild and close this on §10 and §11.
docs(network): the Saruman note defers to the table instead of counti…
docs: the lab domain's six guests are built and joined (#414) (#777)
Merge origin/main into gerrrt/sensor-capture-gro-off
docs: the lab domain's authentication generator runs, and Hicks's vie…
docs: drop a stray conflict marker, and say authgen is in Domain User…
fix(ansible): the four skeleton roles are no-ops against the live dom…
feat(ansible): the gpos role — Deny Tier 0 logon, and the file-share …
feat(ansible): the lab domain's tiers, shares and SOC agents as roles (…
feat(ansible): the gpos role — Deny Tier 0 logon, and the file-share …
feat(ansible): the lab domain's tiers, shares and SOC agents as roles (…
feat(lab): the SOC sees #449's weaknesses: DS-changes auditing, the s…