Anti-jam processing protects GNSS availability by reducing interference energy. Anti-spoof protection addresses false or manipulated navigation signals. Systems exposed to both threats need separate controls for signal availability and navigation-data integrity.
Different threats, different controls
Jamming overwhelms weak satellite signals with interference. Spoofing introduces misleading signals or navigation data. One performance claim should not be used as evidence for the other.
Layered protection
Spatial filtering, receiver monitoring, authenticated navigation data and cross-checks with other sensors can form a broader resilient-PNT architecture.
Select from the mission requirement
Use anti-spoof configurations when trusted position is as important as keeping a fix. Define how alerts, residual signals and receiver outputs will be assessed.
Anti-jam and anti-spoof address different failure modes
| Procurement question | Jamming | Spoofing |
|---|---|---|
| What reaches the receiver? | Interference that competes with weak satellite signals | Counterfeit or manipulated signals that resemble legitimate GNSS |
| Typical system concern | Signal availability and loss of fix | Position, velocity or time integrity |
| Evidence to request | Waveform, input level, geometry, protected bands and suppression result | Threat model, detection or mitigation method, alert behavior and measured output |
| Acceptance boundary | Array, processing electronics, receiver and installation | Receiver, navigation data, sensor cross-checks and host response |
Anti-jam and anti-spoof claims should be reviewed independently even when both functions are packaged in one terminal.
Compare NOVA dual-protection starting configurations
| Model | Array and direction capacity | Published anti-jam value | Published anti-spoof value | SWaP |
|---|---|---|---|---|
| NOVA-AS4 | 4-channel; three interference directions | ≥105 dB single-source suppression; B1 / L1 / E1 | Residual spoofing signal C/N₀ ≤20 dB | 150 × 130 × 22 mm; ≤520 g; ≤13 W |
| NOVA-AS16 | 16 elements; fifteen interference directions | ≥120 dB single-source suppression; B1 / L1 / E1 | Residual spoofing signal C/N₀ ≤20 dB | Ø370 × 53 mm; ≤3.0 kg; ≤40 W |
These values describe published standard starting configurations, not guaranteed platform outcomes. Confirm the waveform, geometry, receiver state, measurement point, software and host behavior for the quoted configuration, then define pass or fail limits through the testing and acceptance framework.
Evaluate anti-spoofing as a layered receiver and system function
| Protection layer | Engineering purpose | Evidence to request |
|---|---|---|
| Signal and measurement checks | Identify inconsistent power, timing, direction, correlation or measurement behavior | Monitored observables, thresholds, alert latency and recorded receiver response |
| Navigation-message authentication | Verify that supported navigation data originates from the stated service | Supported service, receiver compatibility, authentication state and failure behavior |
| Independent cross-checks | Compare GNSS position or time with suitable sensors or complementary references | Source independence, accuracy, update rate, fusion logic and disagreement limits |
| Host-system response | Warn, reject, degrade or recover when GNSS becomes suspect | Interface definition, decision thresholds, logs, fallback mode and recovery criteria |
The European Union Agency for the Space Programme explains that Galileo Open Service Navigation Message Authentication (OSNMA) lets compatible receivers verify that supported Galileo navigation-message data came from the system and was not modified. See the current EUSPA Galileo OSNMA service page. OSNMA adds a data-authentication layer; it does not replace signal checks, independent references or a tested host response.
The European Space Agency Navigation Laboratory lists signal simulation, recording and playback, anomaly simulation and an anti-spoofing test bed among its receiver-evaluation capabilities. See the ESA Navigation Laboratory. Use the resilient-PNT guide to define the full protection architecture and the testing framework to document separate anti-jam and anti-spoof acceptance criteria.
Questions procurement teams ask
How is GNSS spoofing different from jamming?
Jamming raises interference and can prevent a receiver from tracking satellite signals. Spoofing presents false or manipulated signals that may produce a plausible but incorrect position or time. The two threats require different evidence and controls.
Does anti-jam capability prove anti-spoof protection?
No. Interference suppression is not evidence that false navigation signals will be detected or rejected. Ask the supplier to identify the anti-spoof method, receiver behavior, alert output and acceptance test separately.
Does Galileo OSNMA prevent every form of GNSS spoofing?
No. OSNMA helps a compatible receiver verify the authenticity of Galileo navigation-message data. It is one protection layer, not proof that every counterfeit signal or system-level deception will be detected, rejected and handled safely.
What should an OEM request from an anti-spoofing supplier?
Request the threat model, protected constellations and bands, authentication or detection methods, receiver and sensor interfaces, alert behavior, host response, test conditions, residual-signal or integrity criteria and recorded pass/fail outputs for the quoted configuration.
Can anti-spoofing be added without changing the host navigation system?
It depends on the receiver, signal path and interface. Detection is incomplete unless the host has defined behavior for alerts, rejection, degraded operation and recovery. Confirm required RF, data and output changes and the host response before treating a configuration as a retrofit.
Which outputs should be logged in an anti-spoofing acceptance test?
Record a synchronized authentic and counterfeit-signal scenario, authentication state, monitored observables, detection and alert latency, position or timing error, mitigation or rejection behavior, host action, false alarms and recovery. The exact list and pass limits must match the quoted system boundary.