A drone accepts a command only if it fits the mission someone approved.
Drone command links prove that a message came from someone holding the key. They do not prove that the command is one a person actually approved. If a ground station is compromised, it sends whatever an attacker wants, with a valid key.
The gap
- One shared key. MAVLink 2 signing uses a single secret shared by the ground station, autopilot and every connected component, with no rotation, so one compromised node exposes the whole system.
- Rarely switched on. Key distribution and revocation across a fleet has little production tooling, so signing is reported to be rarely switched on.
- The ground station is the soft spot. One 2026 security audit found that a compromised drone can reach back and take over the station that controls the fleet.
The design: mission command authorization
- An accountable person approves a mission: this aircraft, this area, this altitude band, this time window, these commands. That approval becomes a short‑lived token that can only narrow as it is delegated, for example to each drone in a swarm.
- The mission token and a signed trust bundle are loaded before take‑off over a wired link. Approving a change to a mission in flight should happen on a device separate from the ground station.
- A small gate on the drone’s companion computer sits between the radio and the autopilot. Sensitive commands (a new mission, a geofence or parameter change, a payload release) reach the autopilot only if they fit the approved mission. Everything is checked on board, with no ground link needed.
- A command that does not fit is dropped, the drone keeps flying its approved mission, and a signed record of the refusal is kept.
Safety comes first
The gate never sits in the flight‑control loop and is never a safety function. Commands that move the aircraft to a safer state (hold, return to launch, land) are never blocked, and a refusal never cuts power. The trade‑off is stated plainly: because these commands are not blocked, someone holding a stolen link key could still force a landing or a return. Link encryption or signing still protects the radio link; SPT‑Txn answers a different question: was this command approved?
What it would not stop
Jamming, GPS or sensor spoofing, and a compromised autopilot or companion computer are outside what a command check can fix. Neither does it judge whether an approved mission was wise; it records who approved it.
If this is useful to you
We are looking for drone operators, autopilot developers and researchers to review the design and help build a first simulated demonstration.
The same check for plants and machines →
The same check for robots and IoT (design) →
How the token chain works →
rudi@violetskysecurity.com