The storm
Every system that matters now stands in the storm.
The controllers that run the world's water, heat, power and factories were designed for a trusted network inside a locked room. Neither exists any more. Around them are states, criminals, hacktivists and plain bad luck. That is the storm. It does not need to find you. It only needs to find your controller.
What the storm has already done
From the record
One weekend in late July, in more than thirty towns, the controllers that run the water plants stop answering to the people who run them. Passwords are changed. Addresses are changed. Control logic is rewritten, the safety shutdowns are switched off, and the screens the operators can still see are made to lie. In one town the tower cannot fill for over an hour. Two others go to manual. A fourth declares an emergency. Within a week it is at least twelve states. The tools were the vendors' own engineering software, run from rented servers, against controllers anyone could find on the internet. The water stayed safe to drink. Nothing about the controllers made that so.
In the dead of winter, the heating controllers for six hundred apartment buildings begin receiving temperature readings that are not true. They do what controllers do with readings: they act on them. About a hundred thousand people lose heat and hot water for two days in sub-zero weather. Nothing was broken. The controllers were lied to, over a protocol with no way to tell a lie from the truth. The way in was a router nobody had patched.
Eleven days into a war, a company watches eighty thousand of its computers wipe themselves in about three hours. No malware. One stolen administrator credential and the company's own device-management console, doing exactly what it was built to do. The devices in hospitals survived because they were on a different network.
A utility serving two towns, with the staff of a small town, hosts a state-sponsored group for more than three hundred days. The visitors break nothing. They copy the operating procedures and the layout of the grid: what you need to know exactly where to strike, later, at a time of your choosing.
Two days before the new year, a wiper reaches two combined heat-and-power plants and the management system for a fleet of wind and solar generation. It is stopped before the lights go out. The country calls it the largest cyberattack it has seen in years; the US agency that watches these things says it should put every infrastructure operator on notice.
Someone on the internet types a weak password into a dam's web control panel and opens a valve. Five hundred litres a second flow for nearly four hours before anyone notices.
One of the largest retail breaches on record began with a heating and refrigeration contractor's login. The contractor had remote access to watch store temperatures and energy use. From there to forty million card numbers was a matter of network segmentation nobody had done.
Ransomware takes a hospital's building systems: the central monitoring of heating and cooling, the staff door cards, the elevators. Patients keep receiving care, because the equipment itself keeps running without its supervisor. That is what good looks like. The machines kept working when the computer above them was lost.
What it has not done. Yet.
Scenarios
None of these has happened. Every part of them has. The places and companies below are invented; the mechanisms are not.
A city of forty thousand. Its treatment plant's controllers have been quietly owned for months, the way the two-town utility was. On a Friday evening the chemical feeds move and every reading on every screen stays pinned to normal, the way Lviv's did. The operator on shift sees a healthy plant. The same controllers dose the chlorine, the lye and the fluoride. When Milwaukee's treatment failed in 1993, through no attack at all, about four hundred thousand people fell ill and dozens died.
The chillers for a data hall speak a protocol with no passwords, because it never needed any. One evening the setpoints move and the temperature readings do not. The hall has minutes, not hours. The controllers' logs show nothing, because the controllers were told to show nothing.
A control node goes missing from a rural pump house. On a bench two hundred miles away it is opened, its storage copied, its firmware read, and its identity cloned onto a device that rejoins the network as a trusted peer. Nothing on that network can tell the difference. Nothing was designed to.
A machine worth more than the building around it. Underneath its physics sits a rack of supervisor computers with remote-desktop ports, installed by five different vendors. One vendor's support account is on a list that was sold last year. The interlocks are software. The calibration took eleven months.
What the storm teaches
- The door is the boring part. A contractor's login, a default password, a router nobody patched, a management console. Not one case above began with a feat of cryptanalysis.
- Attackers pick a product, then find its owners. Whole fleets of one controller fall together.
- The new tactic is to blind the operator. False readings, disabled alarms, deleted logic. The node that senses and reports the truth is the asset.
- An office breach stops the plant by precaution. The plant that can prove it is still clean keeps running.
- The adversary is already inside, waiting. Denying a foothold beats finding one later.
- Physical hands reach devices. Field equipment is stolen, opened, re-flashed and cloned. Almost no control product has an answer for it.
What stands in it
Storm Agents
You cannot stop the storm. You can decide what stands in it.
Our first product, SA1, is a physically secure embedded system: your agent inside the storm. It runs your equipment, and it gives up nothing when the storm reaches it. It is designed around three promises.
Built like a safe.
A root of trust in the silicon, so it only runs code it has verified, from the first instruction. Nothing outside the processor is ever unencrypted, including DRAM, whether it is powered or not. Its enclosure is designed to detect a breach while powered and respond by evicting its keys and halting, and to refuse to release its keys at the next power-up if it was opened unpowered. It is bound to one owner. Stolen, it yields ciphertext. Opened, it yields nothing. There is no default password, no vendor back door, and no service port to find.
Works like a crew.
You never deploy only one. Nodes are designed to cluster on your own network with no central point or server and no cloud: they elect, replicate, and constantly watch each other. When one fails, or is attacked, the others carry the plant and your own technicians swap in a spare that already knows who it belongs to. Unplug old, plug in new, press go. After onboarding there is no tether to us and no need for an internet connection.
Sold like a component.
Run it as the controller of a plant, or build it into your own machine as its control core. Either way it is one part, designed and built in the United States by a US company, and designed to carry its own security certification so that the product around it inherits it. When your customer asks whether your system is secure, you have an answer you can point to.
What it is not.
It is not a cloud service. Nothing is unhackable, but a Storm Agent is built so that breaking in costs more than what is inside, and so that when you lose a box, you do not lose your plant.
In or out of the real-time loop.
It scales to the job. Keep the real-time loop in your PLC or FPGA and run SA1 above them as the supervisor, or let it take the loop itself: its array of hardware interfaces lets it handle real-time control when you need it to, and stay out of the way when you do not. Either way the security, the clustering and the swap are the same.
Ethernet, USB, Analog, GPIO, I2C, SPI, CAN, Serial, Timers. Adaptable to servos and high-speed control interfaces.
Talk to us: info@stormagents.com