Category: Lessons Learned
-
The check that worked, and was ignored
A 120 GB virtual disk was being moved from SSD to spinning disk. The SSH session running it timed out and dropped. The move kept going on the server, as it should.
-
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.
-
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.
-
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.