Luxailux.ca

Articles · Infrastructure & Cities

The modem that learned to say no

In the KA-SAT attack, no terminal could question the instruction that disabled it. GroundDoor checks every command before it crosses to space, so an unprovable order does not fly.

By Lucian · Lux Automations

The problem

When people picture an attack on a satellite, they picture the sky. The record points the other way. The satellite is rarely the weak point; the ground network is — the stations, consoles and management systems that speak to the satellite and tell the terminals below it what to do.

In February 2022, attackers entered through a misconfigured VPN into the KA-SAT ground management network and pushed a wiper to tens of thousands of modems. The satellite itself was never touched. The ground, not the sky, was the open door. And on the ground’s receiving end, no terminal could question an instruction that disabled it. The modems obeyed because obedience was all they had been given.

Every new constellation and every rented antenna multiplies these crossings. Commercial operators and ground-station services pass commands up and telemetry down through more hands, more consoles and more networks than the early systems ever imagined. Each crossing believes what it is told, in the same unquestioning way.

The technology

GroundDoor is described on its product page in one sentence: a modem that can question an instruction — that is the whole product. The questioning is built from the house engine. Every ground system and operator console holds an issued identity: consoles, stations and services are issued, not assumed, so a command arrives under a name that can be checked.

Command classes are then mandate-checked. Listening and commanding are different keys. A monitoring station may listen, never command, and under GroundDoor its instructions to command do not cross, however they are dressed. The mandate separates watching the sky from ordering it, and the check sits at the crossing before anything travels further.

Every command crossing leaves a signed receipt: who ordered it, under what mandate, when. At the far end, a terminal that can say no completes the design — an instruction that cannot prove itself bounces at the modem instead of being obeyed into silence. Amos checks who is knocking, SeamGuard checks the joins between systems, and every check leaves a signed receipt.

What it changes

For satellite operators and ground-station providers, the change is that commands carry proof with them. A legitimate order, from an identified console acting inside its mandate, crosses and is receipted. An order that cannot establish any of that stops at the door, on the ground, before it can become tens of thousands of silent terminals.

The receipt record changes the aftermath as well. Instead of reconstructing a night of commands from partial logs across several networks, the operator holds a signed account of each crossing: the ordering party, the mandate it acted under, and the time. In a trade where an incident can span countries and providers, a record all parties can read is its own form of order.

Nothing here hardens the satellite itself, and nothing claims the sky is safe. The claim is at the crossing where the known failure happened: commands checked before they cross to space, by identity and by mandate, with a receipt for every one.

See it

GroundDoor checks who talks to a satellite from the ground, and gives the modem a way to say no. GroundDoor — the product page · All the house articles · Lux Automations — ailux.ca