Kybernao Blog·6 articles
Attack-path research, field notes from links that went away, and engineering writing from the people building the cyber brain. Written by the engineers who ran the deployment, not by a content team.
Cloud and platform teams tend to believe operational technology is somebody else's problem. Your compute stands on chillers, switchgear and a building management system, that layer is run as facilities rather than as systems, and the cloud estate above it can usually reach down.
6 articles
Under every cloud estate is a control network nobody inventoried: BMS, CRAC rows, switchgear. Four hops from a cloud role to a cooling row, and no exploit at any step.
An authorization attests that controls were in place. A retest demonstrates the boundary still denies the write this morning. One of those ages badly.
What actually crosses a site boundary in a Kybernao deployment: nine egress classes, four categories with no switch at all, and what still runs when the cloud is gone.
A corporate SSO login should not be able to cool down a 340 MW generator. At one power site it could, in seven hops, and not one of those hops was a vulnerability.
We pull the link for forty-three minutes and count what a cloud-first security stack loses in the first ninety seconds. The list is longer than most architecture diagrams admit.
Testing a plant is not testing a web application. The question is never whether we can break it. It is what we are allowed to prove, where we are allowed to prove it, and who says go.
We publish when we have something measured to say. Clear the filter to see everything we have written so far, or ask an engineer directly.
Dispatch
Path studies, outage post-mortems, and hardware notes. No product announcements dressed as research.
Site design sessions open
Bring one site, one operational environment, or one tactical mission. We will map it, find the routes that matter, and show you the terrain graph built from your own environment.