Field notes
What we learn running managed environments: how a security system gets designed before anything is mounted, why a backup is only real once it has been restored, and what it takes to keep a rack honest. Written by the team that operates them.
Subscribe via RSSAdd up the nameplate ratings on the power supplies in one rack and you will specify three times the power you need. Measure the draw at the wall instead, derate the circuit properly, and let the arithmetic pick the plan.
Read the postCameras are internet-connected computers with a decade-long firmware half-life, mounted where nobody looks. Segmentation is not a hardening extra; it is the design decision that makes every other camera control possible.
Read the postThe green check mark means the job completed. It does not mean the database opens, the application starts, or the business runs on the restored copy. The only proof is a restore, performed on purpose, before you need one.
Read the postAn agent platform that gives each AI teammate its own cloud computer, persistent memory, and logins to your systems is genuinely useful. It is also a privileged account, and it needs an owner, a scope, and a log.
Read the postThese emails reference real recent transactions, use your bank's actual branding, and land in inboxes that already passed basic filtering. Here is how the campaign works and what actually stops it.
Read the postThe controls were never the hard part. Producing a year of evidence that they actually operated is where first audits go wrong — unless the systems that secure you are the same ones that document you.
Read the postClient lists pasted into public chatbots. Contracts summarized on consumer apps. Credentials sent to whatever assistant was open in a browser tab. The habit is already formed — the only open question is where the data lands.
Read the postTell us what your environment looks like and we will tell you what we would do with it — in writing, before you commit to anything.
