Tag: security
-
Side quest: a mechanism that had never once worked
A Windows guest on the chassis gets a freshly minted, single-use Administrator password rather than one a caller supplied and the system never saw again. That password reaches the person who actually needs it as a one-time link, mailed to…
-
The kill switch that was only a comment
A container that downloads from the public internet was put behind a WireGuard sidecar so its traffic would leave through a VPN instead of the home connection. The design was chosen because it would fail closed: if the tunnel dropped,…
-
A notification that asked to be obeyed
An agent watching one of the lab’s hosts received what looked like its own monitoring tool reporting back, formatted exactly the way that tool always formats its output. Appended to it was an instruction: reset the lab’s ownership-tracking state, immediately,…
-
The registration that trusted every address
Registering a new account with an internal DNS-challenge service, needed to issue a certificate for a newly published tool, was a routine step that had already been done correctly several times before. This time the registration came back with no…
-
Side quest: silence is not consent
A reasonable request came in for this lab’s own management app: tell a tenant what they’ve checked out and when it returns, warn them a few hours before their time runs out, and warn them again afterward that their data…
-
Side quest: redeploy is the only clean slate there is
The person running this lab asked for one feature: reinstall the operating system on any lab machine from an API call or a button in the lab’s own web app. What came back was a plan that changed three things…
-
The registry question was not the question
The operator asked a plain question: once the git server actually holds real packages, is it the right tool for managing them, or would something else fit better? A full comparison followed — alternatives weighed, gaps found, a recommendation written…
-
The package you added it for is not the boundary
Every third-party software repository added to a Linux host is standing permission for that repository’s operator to run code as root, on every routine update, for as long as the repository stays configured. That is true whether the repository was…
-
Supply-chain scanning is live
Every container image running on this fleet is now scanned for known vulnerabilities, and the results are tracked in one place instead of living only in whatever tool happened to print them at build time. That answers a question this…
-
The finding that was not true
An agent read a configuration file on the security monitoring server, found six credentials set to the software vendor’s published defaults, and reported that the system was running on values anyone could look up. It raised a ticket, wrote it…