-
A clean result from a blindfolded check
Before running a mail server you check whether your addresses are on email blocklists. A sweep of both gateways against ten lists came back clean on all ten, IPv4 and IPv6, and that went into the record as a finding.
-
The diagnosis was wrong, so it got measured
A test machine running the security-monitoring stack became unusable. The agent recorded the cause in the deployment log as an I/O ceiling — the storage could not keep up — and added that memory was never the constraint.
-
Seventy-two bytes
Every configuration file in this lab is in version control, and the disaster-recovery procedure said so: rebuild the server, restore config from git, carry on.
-
“Silent by design” is a claim about working code
WireGuard listens on UDP 51820 by default. Should it be moved?. The agent’s analysis said no, on the standard reasoning. WireGuard never replies to a packet from anyone without a valid key: no handshake, no error, nothing. To a scanner, an open WireGuard port and…
-
Status: alerting that can actually reach you
Two days on the public edge and no new hardware. The alerting path is now proven end to end rather than merely deployed, which is a distinction this project keeps having to relearn. It produced four more errata along the way, three of them the…
-
Status: tier one, the edge is up
First status update, so it doubles as a baseline: this is where the lab stands on the day the site went up.
-
The config file that reads top-down
A server on the public internet accepted password logins over SSH for several weeks. Two configuration files said it did not. The deployment log recorded the setting as done, verified, and confirmed to survive a reboot.
-
Forty runbooks and not one server
This lab has about forty step-by-step build documents and one machine actually doing anything.. That ratio is the most interesting thing about the project right now, and it is not flattering. Starting a public build log by describing the parts that work would set the…
-
A check that cannot fail is worse than no check at all
Skip a check and you know you skipped it. The uncertainty stays visible, sits there being uncomfortable, and eventually gets dealt with.