Lineage For Anti-Jamming

Defence

6min

When the link dies, what flies the drone?

Every operator knows the moment. The screen goes red. The video stutters. The platform stops responding. Somewhere in the spectrum, someone has decided you do not get to finish your mission today.

This is the reality of contested-spectrum operations. Jammers are cheap. Spoofers are commodity. The encryption stacks protecting most command links today were designed for a quieter world, one without harvest-now-decrypt-later attacks and without a credible quantum threat on a ten-year horizon.

Lineage is built for the world we actually operate in.


What changes for the operator

The promise is simple. The link stays up when other links fail. Every command is verified before the platform acts on it. Forged messages and replays are rejected at the receiver, not flagged for someone to review later. If a message fails authentication, the platform falls back to its last verified guardrail set, geofences, no-fly volumes, fail-safes. Authority defaults to the last known-good state. It never defaults to an unverified instruction.

That last point matters. Most security layers in the C2 stack today are configured to fail open or fail unpredictably under sustained electronic-warfare pressure. Lineage fails secure. The aircraft does not start taking commands from whoever has the loudest transmitter on the frequency.

For operators, the day-to-day experience does not change. No new workflow. No retraining. The link either authenticates and you fly, or it does not and the platform holds within its last verified bounds. The decision is made before the platform acts.

What changes for manufacturers

For platform builders, integration is the question that kills most security upgrades. Lineage is a drop-in software layer. It sits inline between the radio and the flight controller. No firmware changes. No protocol re-engineering. Eight bytes of overhead per packet.

The format-agnostic point is worth dwelling on. MAVLink, STANAG 4586, CRSF, raw video. Lineage does not care. It treats the command stream as an authenticated bit stream and gets out of the way. Manufacturers do not need to pick a side in the protocol wars or commit to a new C2 standard to deploy it.

There is no handshake. That sounds like a small thing until you have watched a TLS session die in a degraded RF environment because the round-trip never completed. Classical handshakes are link-killers in contested spectrum. Lineage authenticates and protects without them.

Time-to-deploy is measured in days, not procurement cycles. For manufacturers shipping platforms now into a market that will face allied post-quantum cryptography deadlines between 2028 and 2031, that matters. The systems being procured today will still be in service when the cryptographic transition lands. Lineage is on the right side of that line. Classical RSA and ECC are not.

The numbers

Resilience was tested under combined electronic-warfare conditions, random loss, bit corruption, burst jamming and reordering applied simultaneously. Lineage delivered 66 percent of commands under a light mixed attack on a surface RF link, 36 percent under moderate attack, and continued to deliver under heavy attack where session-based protocols had been declared dead on the run.

For subsurface acoustic and submarine VLF channels, where classical post-quantum handshake protocols cannot establish a session in the first place, Lineage was the only protocol still passing commands. 46 percent through a jammed VLF link. 44 percent through a sonar-jammed acoustic channel.

Forward secrecy is per message, not per session. Capture exposure is a single message, not a session and not a fleet. If an adversary recovers a key, they recover one message. They do not recover the operation.

What this enables

For the operator, mission completion in spectrum that was previously a no-go.

For the manufacturer, a credible answer to procurement questions about post-quantum readiness and electronic-warfare resilience that does not require redesigning the platform.

For both, the same thing. The link stays alive. The platform finishes the job.

Complete the mission. Regardless of the spectrum.

Secure The Fleet.

Encryption that will outlast the platforms it protects.

Secure The Fleet.

Encryption that will outlast the platforms it protects.

Secure The Fleet.

Encryption that will outlast the platforms it protects.