The future runs on space. We make sure it holds.
More of what you build runs on space every year: timing, comms, logistics, connectivity. It’s fast becoming critical infrastructure. We help you rely on it with confidence: find where you depend on it, harden the ground systems that carry it, and prove it holds when it’s tested.
The whole stack is in scope, the satellite included.
Every orbit you rely on, the ground stations that fly them, and the third parties who build and supply both. One attack surface, and most of it is testable.
Every orbit you depend on, the ground that flies them, the suppliers behind both: one attack surface. The way in is usually the ground.
German wind turbines lost remote monitoring when the 2022 Viasat attack hit a satellite ground network. No satellite touched.
Viasat KA-SAT ↗rise in airline-reported GPS-loss events (2021–2024) as jamming and spoofing spread along flight routes.
IATA ↗Test the whole stack before it’s load-bearing.
Test it before it flies
A satellite is hardware, firmware and a command receiver built by a long supply chain, and once it’s in orbit, you can’t patch it. We test the bus, the payload and the command interfaces before launch, while a finding is still a fix and not a write-off.
Secure the command path
The ground segment isn’t only where an outage starts. It’s how you fly the bird. Compromise it and you can send the satellite commands. We treat mission control and the command chain as the crown jewels they are, the way researchers took over a live satellite in orbit in the Space Force’s Hack-A-Sat.
Map the dependency
You can’t defend a reliance you never mapped. We trace where your operations lean on space (GPS timing under payments and the grid, satellite links behind remote sites and logistics) and the ground systems and terminals that carry them.
Rehearse the outage
Jamming and spoofing never touch your network. They don’t have to. We test how your operation holds when the signal is degraded, spoofed or cut: the fallback, the failure mode, and whether “GPS is down” quietly becomes “we’re down”.
We don’t launch anything or bend the physics of orbit. No one needs to. The offensive, practical work lives in the hardware, the command path, the signal and the dependency.
Looking further out, we’ve threat-modelled the next frontier too: security-by-design for computing that leaves the planet. A threat model for space-based data centres →
Find out what happens when the signal drops.
A dependency map is the cheapest move you can make: it tells you which parts of your operation quietly assume space is always there, and what breaks first when it isn’t. We’ll build it with you, test the ground systems you can actually reach, and tell you honestly how much of this is urgent for you and how much can wait.