GNSS Security

GNSS spoofing & jamming resilience test with conducted RF

Test GPS spoofing detection & jamming resilience with conducted RF in a shielded lab: repeatable spoof and jam signals, no over-the-air transmission.

Updated 2026-07-09
A shielded enclosure combining true constellation, spoofer and jammer onto one conducted path into the receiver

GNSS interference is the fastest-rising threat in positioning, with jamming and spoofing incidents climbing sharply since 2023, and the engineers who have to answer “is our receiver resilient?” face a hard problem: the honest test is to attack a real receiver with real spoofing and jamming signals, and doing that over the air is both illegal and reckless.

The answer the whole field converges on is conducted RF: keep the attack in a cable or a shielded chamber, never on the air. AnyLocate generates the true constellation and the threat on the same controlled path, so you can be aggressive with the attack and safe with the law at once.

Jamming causes the receiver to die; spoofing causes the receiver to lie.

Validate your receiver against spoofing

Understanding how a receiver behaves under attack is the key to detecting the attack, and that requires systematic, repeatable tests of receiver performance in the presence of a spoofer, inside a completely closed system that will not interfere with live GNSS.

Script the attack precisely: a gradual capture that walks the position away without a jump, a time push against a timing receiver, a meaconing replay of recorded signals. Because it is conducted and scripted, you can run the exact same attack against every firmware build and every competing receiver, and compare like for like.

Test jamming and interference resilience

Set a defined j-to-signal ratio and step it up. Measure where the receiver loses lock, whether it flags the interference, and how fast it recovers: the numbers that tell you whether a system will keep positioning through a contested environment.

Build a repeatable resilience test bed

The value is repeatability. Convert real-world incidents into a regression suite of scenarios, keep a library of attacks, and re-run them on demand. Whether you are hardening a receiver, validating a detection algorithm, or proving PNT resilience for critical infrastructure and timing, the same shielded, conducted bench does it safely, with no field range, no spectrum licence, no risk to anyone else’s GPS.

Frequently asked questions

Is it legal to test GPS spoofing?
Transmitting spoofing signals over the air is restricted in most countries. The safe, standard approach is conducted testing: connect the simulator to the receiver by coaxial cable through an attenuator, or work inside a shielded enclosure, so no signal ever reaches open air or real GNSS users.
How do I test a receiver against spoofing without transmitting over the air?
Combine the true constellation and a spoofing scenario onto the same conducted RF path into the receiver under test, then ramp the spoofer's power and offset. Everything stays in the cable or the chamber: repeatable, measurable, and legal.
What is the difference between jamming and spoofing?
Jamming makes the receiver die: it drowns the signal so the unit loses its fix. Spoofing makes the receiver lie: it feeds a convincing false signal so the unit reports a wrong position while believing it is fine. You test resilience to both differently.
How do I validate a spoofing-detection algorithm?
A detector is only as good as the attacks you can reproduce. Script a battery of spoofing and meaconing scenarios (gradual capture, position pull-off, time push) and replay them identically across algorithm versions to prove detection and measure false alarms.

Related use cases

GNSS receiver testing: TTFF, sensitivity, production test
Bench-test drone GPS failsafe & return-to-home, no flying
Try it on your own signals
Run this scenario — and yours — on a software-defined GNSS simulator you can actually afford.
See pricing →