Fact-checked by Grok 2 weeks ago

Selective availability anti-spoofing module

The Selective Availability Anti-Spoofing Module (SAASM) is a specialized hardware and software component integrated into military Global Positioning System (GPS) receivers to enable decryption of the encrypted precise positioning service (PPS) signals, specifically the Y-code variant of the P-code, thereby granting authorized users access to high-accuracy pseudorange measurements while denying them to unauthorized parties. Developed as an upgrade to earlier GPS security measures, SAASM incorporates over-the-air rekeying capabilities to periodically update cryptographic keys, enhancing resistance to signal spoofing and tampering by adversaries who might broadcast false GPS signals to mislead receivers. Although its name references Selective Availability (SA)—a now-discontinued policy from 1990 to 2000 that intentionally degraded civilian GPS accuracy by up to 100 meters to maintain a military advantage—SAASM primarily focuses on anti-spoofing through encryption rather than accuracy degradation, with SA's termination in 2000 improving global civilian access without compromising SAASM's core functions. This module has been pivotal in modernizing U.S. Department of Defense GPS applications, supporting platforms from precision-guided munitions to inertial navigation systems, and remains a foundational element of secure GNSS operations amid evolving threats like jamming and meaconing.

Overview

Definition and Core Functionality

The Selective Availability Anti-Spoofing Module (SAASM) is a standardized component designed for integration into U.S. and authorized government GPS receivers, enabling decryption of the encrypted Precise (P(Y)) code signal transmitted by GPS satellites. This module facilitates access to high-accuracy positioning, navigation, and timing (PNT) data that is denied to unauthorized users through cryptographic means. SAASM receivers authenticate and process the Y-code, a encrypted variant of the legacy P-code activated via the Anti-Spoofing (AS) feature implemented by the U.S. Department of Defense to protect against signal imitation. At its core, SAASM's primary functionality involves secure signal decryption using embedded cryptographic processors that handle classified keys, ensuring only equipped receivers can resolve the full precision of military GPS signals, which offer sub-meter accuracy under nominal conditions compared to the coarser Standard Positioning Service (SPS) available to civilians. A key operational feature is over-the-air rekeying (OTAR), which allows remote updating of encryption keys without physical access to the receiver, enhancing long-term against key compromise while maintaining compatibility with (NSA) key management systems. This modular architecture supports integration across diverse platforms, from airborne systems to ground vehicles, by encapsulating all classified GPS processing in a tamper-resistant unit that can interface with host receiver hardware. The anti-spoofing capability stems from the cryptographic verification inherent in Y-code decryption: spoofed signals lacking valid encryption cannot be authenticated, prompting the receiver to reject or flag them, thereby mitigating risks of false position fixes induced by adversarial signal injection. Unlike , which overwhelms signals with noise, spoofing requires precise replication of GPS waveforms; SAASM counters this by demanding computational infeasibility for unauthorized entities to generate compliant encrypted (PRN) codes in . This functionality, while foundational to SAASM, positions it as a bridge to modern enhancements like M-code, but remains reliant on periodic key refreshes to sustain efficacy against evolving threats.

Relation to GPS Signal Structure

The GPS signal structure incorporates multiple components transmitted on L1 (1575.42 MHz) and (1227.60 MHz) carrier frequencies, including the civilian coarse/acquisition () code modulated solely on L1 at a 1.023 MHz chipping rate for public access, and the () code originally intended for both frequencies at a 10.23 MHz chipping rate to enable higher accuracy positioning. To counter spoofing threats, the Department of Defense implemented anti-spoofing by encrypting the P code into the P(Y) code starting in the early , overlaying a classified cryptographic sequence that renders the signal unintelligible without decryption, while preserving the underlying PRN structure for authorized users. The P(Y) code thus forms the secure backbone of the GPS signal, coexisting in the same spectrum as civil signals but requiring key-based decryption to extract navigation data, such as satellite ephemeris and time, with sub-meter potential under optimal conditions. SAASM integrates directly with this encrypted signal architecture by providing hardware and firmware capable of securely storing and applying decryption keys to recover the P(Y) code's sequences, enabling with the receiver's replica code for precise time-of-arrival measurements essential to . Unlike C/A-only receivers limited to the open L1 signal, SAASM-equipped devices authenticate the signal's origin by verifying the decryption output against expected P-code properties, mitigating risks from replicated civilian signals that lack the Y-code layer. This relation underscores SAASM's dependence on the GPS constellation's dual-code structure, where the higher-rate P(Y) modulation enhances processing gain (approximately 24 dB over ) for improved resistance, though SAASM itself does not alter the transmitted signal but rather the receiver-side processing to exploit it securely.

Historical Development

Origins in GPS Security Needs

The U.S. Department of Defense initiated the (GPS) program in 1973 to deliver precise positioning, navigation, and timing capabilities tailored for military superiority, recognizing early the vulnerabilities of unencrypted satellite signals to exploitation by adversaries. Central security imperatives included preventing denial of service through or via spoofing, where hostile entities could broadcast falsified signals to mislead receivers and disrupt operations. To address these threats, GPS incorporated a dual-signal structure: the coarse/acquisition () code for broader access with intentional degradation via Selective Availability, and the precise () code reserved for military use, encrypted as the Y-code to enable signal and resist imitation. This anti-spoofing mechanism, operational in the P(Y)-code by , ensured that only equipped receivers could verify legitimate transmissions, thereby maintaining causal reliability in contested environments where false signals could induce erroneous guidance for weapons or forces. The Selective Availability Anti-Spoofing Module (SAASM) originated as a response to the practical challenges of implementing and sustaining this across diverse receivers, particularly the need for secure, field-updatable cryptographic s without logistical vulnerabilities. Traditional decryption relied on static keys vulnerable to compromise, prompting development of a modular that integrated Y-code decryption with over-the-air (OTAR), allowing remote key rotation to counter interception or capture risks. In , the selected SAASM as the standardized security architecture to evolve GPS , prioritizing , tamper resistance, and adaptability to emerging threats like advanced . By modularizing anti-spoofing functions, SAASM facilitated integration into legacy and new platforms, ensuring military users retained access to undenied precision amid policy shifts, such as the 2000 discontinuation of Selective Availability degradation, while upholding the core objective of verifiable against deception. This approach reflected first-principles for causal : authenticating signal origins through cryptographic means to preserve operational trust, rather than relying solely on signal strength or .

Introduction and Initial Deployment

The Selective Availability Anti-Spoofing Module (SAASM) represents a cryptographic and designed to secure GPS receivers against spoofing by enabling decryption of the encrypted P(Y)-code signal, while incorporating over-the-air rekeying for updated encryption keys without physical access to receivers. Selected by the in as the standard security upgrade for GPS systems, SAASM addressed vulnerabilities in prior anti-spoofing measures, which relied on fixed keys vulnerable to compromise, by implementing a compatible with existing receiver . This selection stemmed from post-Cold War assessments of GPS denial threats, prioritizing causal protections through dynamic over static . Initial deployment of SAASM-equipped receivers occurred in the early , integrated into precision-guided munitions and platform navigation systems to ensure access to full GPS accuracy amid rising concerns over signal and in contested environments. A pivotal milestone came with a Department of Defense directive effective October 1, 2002, mandating that all military GPS acquisitions incorporate SAASM compliance, effectively phasing out legacy receivers dependent on outdated decryption methods. This transition facilitated fielding in systems such as smart weapons, where SAASM modules replaced prior security chips, enhancing tamper resistance and operational reliability without altering core GPS signal structures. By fiscal year 2006, SAASM achieved broader mandatory adoption, requiring in all newly fielded GPS equipment to standardize anti-spoofing across services, with initial operational capabilities demonstrated in systems like the Combat Survivor Evader Locator (CSEL) by 2006. Early implementations focused on and ground platforms, yielding empirical improvements in signal , though challenges included higher power consumption and costs compared to unencrypted receivers. Deployment data from this period indicate over 100,000 SAASM units procured by 2005, reflecting accelerated production to meet Joint Requirements Oversight Council mandates for secure positioning in high-threat scenarios.

Key Policy and Technological Milestones

The of the Selective Availability Anti-Spoofing Module (SAASM) began in the mid-1990s under the GPS Program Office to address vulnerabilities in legacy GPS receiver security architectures, particularly the need for secure decryption of the encrypted P(Y)-code signal introduced on GPS satellites starting January 31, 1994. This initiative focused on enabling over-the-air rekeying (OTAR) of cryptographic keys, compatibility with Type 1 standards, and modular integration into existing receivers to mitigate spoofing risks without relying on outdated black-box . In 1998, the endorsed SAASM as the standard for future military GPS user equipment, marking a pivotal technological shift toward tamper-resistant modules that could authenticate signals and prevent unauthorized access or replication. Policy reinforcement followed with Department of Defense directives emphasizing secure GPS for precision-guided munitions and front-line systems, culminating in GPS Wing Policy requiring the cessation of non-SAASM receiver fielding after October 1, 2002, and mandatory use of SAASM-based equipment thereafter to ensure anti-spoofing integrity. Initial deliveries of SAASM-capable receivers to U.S. warfighters occurred in , allowing operational exploitation of precise, encrypted despite ongoing challenges in full OTAR implementation and . By this point, SAASM had demonstrated operational in force development evaluations, though services noted needs for improved and training; full operational capability assessments confirmed its suitability for denying adversaries access to military-grade accuracy. Subsequent milestones included integration mandates for new systems, such as requiring precise positioning service via SAASM or its successor M-code in front-line weapons by 2007, reflecting evolving threats from and spoofing in contested environments. Over time, SAASM fielding exceeded 2 million units across U.S. and allied forces, serving as the foundational security layer until phased transitions to modernized GPS architectures like M-code Increment 1 achieved initial operational capability in the .

Technical Architecture

Encryption Mechanisms and Y-Code Decryption

The Y-code, also known as the P(Y)-code, represents the encrypted form of the GPS (P) code, generated through modulo-2 addition ( operation) between the P-code and a classified pseudorandom keystream derived from secret daily-changing keys. This keystream, commonly referred to as the W-code, is produced using symmetric algorithms that ensure the resulting Y-code appears as a different sequence, inaccessible without the corresponding keys. The process, activated to counter spoofing threats, authenticates the signal's origin by restricting precise ranging data to authorized users, as receivers can only track the less secure C/A-code. SAASM modules enable Y-code decryption in compatible GPS receivers by integrating secure cryptographic capable of storing and applying classified keys to reverse the . Decryption involves generating the identical W-code keystream from the loaded keys and performing another modulo-2 with the received Y-code, recovering the original P-code for high-fidelity pseudorange calculations. This operation occurs only after receiver authentication, leveraging unique device identifiers to verify eligibility against the GPS control segment. Keys are handled as "black" (encrypted) variants to permit secure over-the-air distribution without exposing "" secrets, with daily cryptovariable updates ensuring periodic rotation for sustained security. The SAASM architecture employs tamper-resistant components to protect key storage and cryptographic computations, mitigating risks from physical compromise or . By confirming the P-code's integrity post-decryption, SAASM provides robust anti-spoofing, as replicated signals lacking the precise would fail and yield inconsistent ranging data. While full algorithmic details remain classified, the mechanism's reliance on symmetric keys and pseudorandom streams has been effective since the Y-code's implementation in the , predating widespread spoofing concerns.

Over-the-Air Rekeying Process

The over-the-air rekeying (OTAR) process in the Selective Availability Anti-Spoofing Module (SAASM) facilitates the remote distribution and installation of cryptographic keys for decrypting the encrypted P(Y) GPS signal, eliminating the need for physical key loading in fielded receivers. This capability relies on unclassified "black" , which are derived from classified "red" during but can be securely transmitted over unclassified channels, contrasting with earlier systems that required classified red key handling and manual insertion. OTAR supports periodic key rotation to counter potential compromises, ensuring continued access to precise positioning service () for authorized military users in isolated or deployed environments. Technically, the process begins with the GPS control segment generating new black keys and uploading them for broadcast via the GPS navigation data message, where they are encrypted using the receivers' current (outgoing) keys as a superset of over-the-air distribution (OTAD). Receivers, equipped with SAASM-compliant hardware like the Key Data Processor (KDP), authenticate the , decrypt the new keys using resident cryptographic software and the existing key set, and then load them to enable decryption of subsequent Y-code signals. This mechanism was enabled by control segment upgrades, such as Architecture Evolution Plan (AEP) Version 5.6, which supported OTAR operations tested during the Multi-Service Operational Test and Evaluation (MOT&E) in August 2011, confirming operational effectiveness for amid threats. OTAR simplifies by streamlining distribution, storage, expiration, and disposal, reducing logistical burdens compared to physical rekeying and enabling unclassified production while preserving through anti-tamper features and black key transitions. In practice, it integrates with devices such as the (DAGR) and is validated using tools like the SAASM Integrated System Evaluator and Reporter (SAASMISER) for simulated signal testing, though operational procedures emphasize training for crypto-ignition and concepts of operations to maximize reliability. This process enhances flexibility for GPS users, allowing timely updates without compromising forward-deployed assets.

Integration with Receiver Hardware

The (SAASM) is implemented as a dedicated component within GPS , typically as a self-contained microchip or pluggable card that interfaces with the receiver's core and RF frontend elements. This enables retrofitting into legacy systems or embedding in new platforms, such as hand-held devices, inertial navigation systems (), and vehicle-mounted units, without requiring a complete overhaul of the host . For instance, SAASM modules like ' GEM-V are connected via standard interfaces including dual-port for high-speed data exchange or serial ports compliant with ICD-GPS-155, allowing the module to receive pre-decrypted or correlated GPS signal data from the receiver's correlators. Integration involves partitioning the receiver architecture into secure domains: a "red" side for classified cryptographic operations, a "yellow" side for key handling and over-the-air rekeying (OTAR), and a "green" side for unclassified navigation computations, ensuring that sensitive decryption processes remain isolated from potentially compromised host components. The SAASM hardware performs Y-code decryption on post-correlation measurements supplied by the receiver's digital signal processor, authenticates the signal against spoofing via embedded cross-authentication checks, and outputs verified pseudoranges, velocities, and time data back to the host via the interface. This separation enhances security by confining crypto functions to tamper-resistant hardware certified under FIPS 140-2 Level 3 or higher standards, while the receiver handles RF downconversion, acquisition, and tracking of both C/A and P(Y) signals. In practice, SAASM integration requires compliance with specifications, including the SAASM Card Integration Program, which standardizes electrical, mechanical, and software interfaces for interoperability across vendors like and . Examples include the NavAssure SAASM , which attaches externally to radios via serial links for portable applications, or onboard implementations in INS units like the INS-20, where SAASM fuses secure GPS inputs with inertial data through synchronized timing interfaces to maintain positioning during . Challenges in integration include managing size, weight, and power (SWaP) constraints—SAASM modules often consume 1-5 watts and occupy volumes under 20 cm³—along with ensuring electromagnetic compatibility and rigorous testing for OTAR key loading without exposing keys.

Security and Operational Features

Anti-Spoofing Protections

The Selective Availability Anti-Spoofing Module (SAASM) primarily counters GPS spoofing by enabling receivers to decrypt and authenticate the encrypted P(Y)-code signal transmitted on the GPS L1 and L2 frequencies, which is the military's precise positioning service. Spoofing attacks typically involve broadcasting counterfeit civilian C/A-code signals to mislead receivers, but SAASM-equipped devices reject such signals by exclusively tracking the Y-code—a classified encryption of the P-code using a secret daily changing key—verifying authenticity through successful decryption. This cryptographic authentication ensures that only genuine satellite signals, protected by the U.S. government's encryption, can be processed, rendering replicated unencrypted or incorrectly encrypted signals unusable. SAASM incorporates over-the-air rekeying (OTAR) to periodically update decryption keys via secure uplinks from ground stations or aircraft, minimizing vulnerability windows where an adversary might exploit a compromised key. This process, compliant with National Security Agency standards, allows keys to be refreshed without physical access to the receiver, enhancing resilience against key extraction attempts. Receivers must possess the current valid key to synchronize with the Y-code's pseudorandom noise sequence, which operates at a 10.23 MHz chipping rate for high-precision ranging, further complicating spoofing efforts that require precise replication of both the code and carrier phase. Hardware-level safeguards in SAASM modules include tamper-resistant coatings and self-destructive mechanisms to prevent forensic analysis or by adversaries seeking to derive keys or signal parameters. These physical protections complement the cryptographic ones, ensuring that even captured modules cannot be exploited to generate spoofing waveforms. In operational testing, SAASM has demonstrated effective rejection of spoofed signals in controlled environments, maintaining positioning accuracy within meters under simulated attacks. However, its reliance on pre-loaded keys and OTAR links introduces potential single points of failure if channels are jammed or intercepted, though this is mitigated by fallback to coarse acquisition aids during transitions.

Compatibility with Anti-Jamming Technologies

SAASM provides cryptographic to verify GPS signal legitimacy, addressing spoofing threats through rather than mitigation, which is the domain of anti-jamming technologies. These protections are complementary, as overwhelms signals with to deny service, while spoofing involves deceptive but authenticated-like signals; SAASM does not confer inherent jamming resistance but enables receivers to process verified signals amid when paired with anti-jam . Military SAASM receivers routinely integrate with anti-jamming systems, particularly Controlled Reception Pattern Antennas (CRPAs), which employ adaptive and null-steering across multiple elements to attenuate jammers by up to 40-50 dB while maintaining satellite visibility. ' MPE receivers, for example, support both Fixed Reception Pattern Antennas (FRPAs) and nulling CRPAs, allowing dynamic adjustment to hostile environments without compromising SAASM's Y-code decryption. Similarly, Communications' NavGuard anti-jam units, offering 4- to 7-channel processing for L1/L2 bands, explicitly interface with SAASM-compliant GPS modules to deliver size, weight, and power (SWaP)-optimized protection for platforms like UAVs and missiles. This synergy has been standard in U.S. military applications since SAASM's enforcement for new deployments after October 2006, with systems like BAE's Integrated GPS Anti-Jam System (IGAS) embedding CRPA-derived nulling in compact forms for munitions, ensuring authenticated positioning persists under broadband jamming exceeding 100 dBW. Compatibility extends to software-defined enhancements, where receiver firmware processes CRPA outputs prior to SAASM authentication, minimizing latency in high-threat scenarios as validated in operational tests.

Performance Metrics and Reliability

SAASM-equipped GPS receivers achieve position accuracy typically below 6 meters horizontal in mode, surpassing limits of around 6 meters , depending on satellite geometry and environmental factors. In specialized configurations, such as (SDGPS) or wide-area augmentation, accuracies improve to under 2 meters (CEP). For real-time kinematic (RTK) SAASM implementations, centimeter-level precision is attainable, enabling applications in unmanned systems. Acquisition performance includes time-to-first-fix under 10 seconds for hot starts in some modules, with support for 12-channel all-in-view tracking to maintain signal lock amid . Anti-spoofing effectiveness stems from Y-code decryption requirements, rendering spoofed civilian signals ineffective for access and providing tamper-resistant authentication, though efficacy depends on timely over-the-air . Reliability metrics for SAASM-integrated systems demonstrate (MTBF) exceeding 20,000 hours in airborne receivers, with some ground-based units surpassing 70,000 hours under standard conditions. Multi-service operational testing in confirmed SAASM's overall operational effectiveness and suitability for use, particularly in contested environments, though sustained performance requires rigorous and training to mitigate procedural vulnerabilities. Limitations include dependency on crypto-key loading for full anti-spoofing resilience, with incomplete integration in broader GPS architectures potentially affecting enterprise-wide reliability.

Military Implementation and Impact

Adoption in U.S. and Allied Forces

The U.S. Department of Defense mandated the integration of SAASM into all newly procured GPS starting October 1, 2002, prohibiting purchases of non-compliant receivers to ensure secure access to the encrypted P(Y) signal. This policy extended to full fielding requirements by October 2006 for all new GPS systems using Precise Positioning Service (PPS), replacing legacy security chips vulnerable to cryptographic obsolescence. SAASM adoption accelerated the upgrade of existing platforms, with tamper-proof modules installed in precision-guided munitions and smart weapons as early as 2002 to mitigate spoofing risks during operations. By the mid-2000s, SAASM-equipped receivers became standard across U.S. armed services, including the (DAGR) for dismounted soldiers and integrated systems in , vehicles, and naval platforms. Manufacturers like deployed SAASM in low-power, anti-jam receivers for major weapons programs, enabling over-the-air rekeying and authenticated PPS signals in contested environments. The module's widespread implementation enhanced operational reliability, with DOT&E assessments confirming its role in U.S. GPS architecture through the , bridging to subsequent M-code upgrades. Allied forces gained access to SAASM through U.S. Foreign Military Sales (FMS) under strict export controls outlined in DSCA policies, categorizing nations into groups based on interoperability needs—Group A allies like NATO members (e.g., UK, Canada) received full PPS/SAASM capabilities for joint operations. Products such as Mayflower's NavAssure series were authorized for FMS to approved partners, supporting coalition navigation warfare while limiting proliferation risks via the Arms Export Control Act. This selective distribution ensured allied equipment compatibility with U.S. forces, as verified in GPS enterprise reports emphasizing shared SAASM functions in authorized user equipment.

Role in Combat and Precision Operations

The Selective Availability Anti-Spoofing Module (SAASM) enables U.S. and allied military forces to access encrypted P(Y)-code , delivering sub-meter essential for real-time targeting and maneuver in contested environments. By verifying signal authenticity through decryption, SAASM mitigates spoofing threats, where adversaries could otherwise transmit false GPS data to divert assets or munitions. This capability proved critical during Operations Enduring Freedom and Iraqi Freedom, where military-grade GPS receivers, incorporating SAASM precursors and early implementations, supported strikes from standoff distances, reducing reliance on forward observers and minimizing exposure to enemy fire. In precision-guided munitions (PGMs), SAASM-equipped receivers integrate into systems like Joint Direct Attack Munitions (JDAM) and guided shells, achieving (CEP) accuracies under 5 meters even amid interference. For instance, ' SAASM-based receivers have been deployed in major weapons platforms for precision-guided bombs and , enabling single-weapon neutralization—a shift from earlier conflicts requiring multiple unguided projectiles. This was evident in Iraqi Freedom operations starting in 2003, where GPS-guided PGMs destroyed hardened targets with one strike, conserving and enhancing operational tempo. SAASM's over-the-air rekeying further sustains combat utility by allowing secure signal updates without physical access, vital for prolonged engagements like those in from 2001 onward. However, vulnerabilities emerged, such as a 2010 software glitch affecting 8,000–10,000 SAASM units across weapons systems, temporarily sidelining some PGMs until patched, underscoring the module's centrality to force projection. Overall, SAASM's role has amplified the efficacy of , synchronizing joint fires and troop movements while denying adversaries similar precision advantages.

Export Controls and International Use

The Selective Availability Anti-Spoofing Module (SAASM) and associated GPS receiver technologies are classified as defense articles under (USML) Category XII, subjecting them to strict controls under the (ITAR). These regulations govern the manufacture, export, and temporary import of such items to prevent unauthorized access to encrypted military , with violations potentially leading to penalties under the (AECA). SAASM circuit boards and microchips, being non-commercial and capable of decrypting precision GPS locations, require specific U.S. government approvals for any transfer, including to domestic entities beyond cleared military users. Export of SAASM-equipped systems, such as Embedded Global Positioning System/Inertial Navigation Systems (EGI), occurs primarily through the (FMS) program administered by the (DSCA), with notifications published in the for congressional review. Under Section 30 of the AECA, approvals for SAASM chip coding and integration have been delegated from DSCA to the U.S. Life Cycle Management Center, facilitating controlled transfers to vetted allies while maintaining end-use monitoring. For instance, SAASM-based GPS receivers have been included in arms sales packages to partners, often bundled with inertial navigation for secure military applications, but only after verifying compliance with U.S. security criteria. International use of SAASM is confined to U.S. military services and select allies under bilateral or multilateral security agreements, such as those with nations or members eligible for FMS. This restriction ensures that the anti-spoofing and capabilities remain protected from risks, with technology transfers limited to integrated hardware like SAASM-enabled receivers rather than standalone modules. Non-allied nations are generally ineligible, as ITAR prohibits exports that could compromise U.S. interests, including potential reverse-engineering of Y-code decryption. Ongoing policy memoranda from DSCA, such as those updating processing for Letters of , reinforce these controls amid transitions to successor technologies like M-code.

Modernization and Successors

Transition from SAASM to M-Code

The transition to M-Code represents an evolution in U.S. military GPS capabilities, replacing the Selective Availability Anti-Spoofing Module (SAASM) architecture with a more robust signal designed for enhanced resistance to jamming and spoofing. M-Code, transmitted on the and frequencies with additional power allocation via ground-based spot beams, delivers higher effective signal strength—up to 10 dB greater than legacy P(Y)-code signals processed by SAASM—enabling better performance in contested environments. This upgrade addresses limitations in SAASM, which relies on over-the-air for but lacks the inherent power advantages and modern of M-Code. Development of M-Code receivers began as part of the GPS modernization effort outlined in the early , with plans to upgrade SAASM hardware to process the new signal starting in fiscal year 2000, aligning with satellite deployments. The Military GPS User Equipment (MGUE) program drives receiver modernization, transitioning platforms from SAASM-based systems to M-Code-capable ones, though delays in M-Code card development have impacted timelines for integrated weapon systems. Vendors have facilitated this shift through modular designs; for instance, Honeywell's Embedded (EGI) allows swapping the SAASM card for an M-Code equivalent, while ' Enhanced D3 receiver supports backward compatibility and direct upgrades within existing vehicle architectures. By February 2024, the M-Code signal achieved global availability following the activation of GPS III satellites, enabling operational testing for U.S. and allied forces. Fielding accelerated in 2025, with the U.S. Army becoming the first service to deploy M-Code across ground, munitions, and domains, supported by partnerships for assured . advanced this further with demonstrations of M-Code Increment 2 receivers in October 2024, offering improved flexibility over Increment 1 and SAASM baselines, and introduced new receiver series in June 2025 for broader integration. Despite progress, full constellation coverage and receiver proliferation face ongoing challenges from program delays, with targeting wider operational fielding by late 2025.

Ongoing GPS Constellation Upgrades

The GPS constellation's ongoing upgrades center on the progressive rollout of GPS III satellites equipped with the Military Code (M-Code) signal, which supersedes the legacy P(Y)-code used in Selective Availability Anti-Spoofing Module (SAASM) systems by providing enhanced digital and resistance to spoofing through rapid signal rekeying and improved encryption. As of October 2025, six operational GPS III satellites contribute to a hybrid constellation blending older blocks with modernized assets, enabling partial M-Code availability for receivers while full constellation-wide capability remains in development pending additional launches and ground segment integration. Key milestones include the accelerated launch of GPS III Space Vehicle 08 (SV-08) on May 30, , via from , which demonstrated expedited deployment to bolster resilient positioning amid contested environments. This follows the SV-07 launch earlier in , with M-Code payloads on these satellites delivering up to eight times greater anti-jamming and three times improved accuracy over prior generations, directly supporting anti-spoofing by authenticating signals against adversarial replication. Concurrent ground upgrades under the Next Generation Operational Control System (OCX) Block 3F, accepted by the U.S. in July , operationalize M-Code features including secure geolocation and dynamic signal management to counter spoofing threats. Future enhancements shift to the GPS IIIF series, with initial launches projected for 2027 and production contracts awarded in May 2025 for additional units at $509.7 million, incorporating a fully digital navigation , 60 times enhanced anti-jamming resistance via higher , and integrated search-and-rescue transponders that indirectly bolster system integrity against spoofing by diversifying payload verification. These satellites maintain with SAASM-era receivers during transition but prioritize M-Code for new , addressing vulnerabilities in older by enabling constellation-wide cross-linking for detection and signal uploads. Delays in OCX deployment have paced M-Code activation, yet 2025 activations on GPS III assets mark a pivotal phase in hardening the constellation against advanced , with full efficacy dependent on completing 22 IIIF units through 2037.

Challenges in Next-Generation Deployment

The transition from SAASM to M-Code, intended to enhance anti-spoofing resilience through stronger encryption and capabilities, has encountered persistent delays in achieving full operational capability. As of September 2024, the U.S. Department of Defense's GPS modernization efforts, including M-Code signal deployment, have faced significant development challenges leading to cost overruns and schedule slips across multiple programs. The highlighted that while satellite-based M-Code transmission progressed, ground control systems and user equipment lagged, postponing secure signal delivery to military users. A primary hurdle involves scaling production and certification of M-Code-compatible receivers for diverse platforms, from ground vehicles to aircraft. Production delays for these receivers have slowed adoption, exacerbating vulnerabilities to jamming and spoofing in contested environments, as legacy SAASM hardware remains in widespread use but is no longer procurable under DoD policy. Transition timelines extend years due to technical integration issues, such as adapting size, weight, and power (SWaP)-constrained systems and ensuring cryptographic key management across networks. For instance, efforts to retrofit over 700 platforms have required resolving application-specific integrated circuit (ASIC) development bottlenecks, with initial deliveries like BAE Systems' NavGuide-M models projected no earlier than 2025. Logistical and economic barriers compound these technical issues, including the high costs of retrofitting or replacing millions of receivers across U.S. and allied inventories, alongside constraints for secure components. During the phased rollout, SAASM-M-Code operations interim spoofing exploits if not all assets synchronously, as adversaries could unmodernized segments. The GAO assessed significant persisting in fielding, potentially delaying warfighter access to jam-resistant positioning, , and timing (PNT) until beyond initial 2023 targets. These challenges underscore the need for accelerated testing protocols and alternative PNT backups to mitigate deployment gaps.

Criticisms and Limitations

Technical Vulnerabilities and Potential Exploits

SAASM-equipped GPS receivers, despite their cryptographic of the encrypted P(Y)-code signal, retain susceptibility to as a primary technical vulnerability. The underlying operate at low power levels (approximately -160 dBW at the receiver), making them prone to denial-of-service attacks via from jammers that overpower legitimate transmissions, preventing signal acquisition regardless of anti-spoofing measures. This limitation stems from the signal structure rather than the module itself, with field tests demonstrating that even modest jammers can disrupt SAASM systems lacking integrated anti-jam antennas or controlled reception pattern arrays. Key management processes introduce exploitable risks due to the reliance on pre-loaded cryptographic keys for decryption and . SAASM requires secure loading of daily session keys derived from master keys, along with annual updates to the Black Key Algorithm Update Parameter (BKAUPD), typically via physical fill devices or limited over-the-air methods; failure to update keys within timelines (e.g., 14-30 days for operational keys) forces fallback to unencrypted C/A-code, negating anti-spoofing. Adversaries could exploit this through targeted disruptions to in dynamic warfare scenarios, such as supply line interdiction, potentially stranding units without authenticated positioning for extended periods. Physical capture of a keyed poses a theoretical of key extraction, though the module's tamper-resistant design—incorporating features like secure boot and encrypted storage—mitigates but does not eliminate insider or advanced forensic threats. Software and integration vulnerabilities in host receivers amplify potential exploits, particularly in networked or embedded systems. Firmware bugs or unpatched interfaces could enable remote code execution or data manipulation, bypassing the SAASM module's isolation; while the core crypto processor resists direct attacks, upstream signal processing or downstream applications remain exposed to injection of falsified ephemeris or timing data. Demonstrated GPS software attacks, such as navigation message exploits causing receiver resets or desynchronization, highlight this vector, though primarily validated on civilian hardware—military implementations face analogous risks without rigorous air-gapping. Supply chain compromises during module production, including potential insertion of backdoors, represent another unverified but plausible threat given historical concerns in defense electronics. These limitations have prompted critiques that SAASM's static keying and L1-band focus inadequately counter evolving threats like coordinated jamming-spoofing hybrids observed in exercises and real-world incidents, such as GPS disruptions affecting military assets in 2021. No public compromises of SAASM keys or modules have been documented, underscoring their robustness relative to GPS, but the system's design trade-offs—prioritizing authentication over resilience in high-threat spectra—necessitate augmentation with inertial aids or transition to successors like M-code for comprehensive protection.

Economic and Logistical Costs

The implementation of the Selective Availability Anti-Spoofing Module (SAASM) imposed substantial economic burdens on U.S. procurement, primarily through elevated unit costs for secure GPS receivers compared to legacy or civilian-grade systems. The anti-tamper chip integral to SAASM functionality drove these premiums, as it required specialized hardware resistant to and physical compromise. For guided projectile applications, SAASM receivers were estimated at approximately $2,000 per unit in large-volume orders, rising to over $5,000 for smaller batches, exceeding costs of conventional receivers without such . Broader fleet upgrades to SAASM compatibility across selected GPS systems were forecasted to total around $1 billion, reflecting the scale of retrofitting precision-guided munitions and platform integrations. Logistically, SAASM deployment demanded extensive rekeying and certification processes, though its over-the-air rekeying capability mitigated some prior dependencies on physically distributing classified "red keys," thereby streamlining sustainment compared to pre-SAASM eras. Nonetheless, upgrading vast inventories—encompassing millions of fielded receivers across Army, Air Force, and other services—presented persistent challenges, including software-hardware incompatibilities that disrupted operations. In 2010, for example, more than 8,000 deployed receivers failed compatibility tests after a GPS signal upgrade, necessitating urgent sole-source fixes costing $900,000. These issues compounded sustainment demands, as the sheer volume of legacy equipment required phased replacements or modifications, straining supply chains and training pipelines while DoD pursued cost-reduction initiatives that yielded an estimated $100 million in savings via miniaturized designs.

Debates on Efficacy Against Advanced Threats

SAASM's cryptographic mechanism authenticates GPS P(Y)-code signals, enabling military receivers to reject spoofed transmissions lacking valid decryption keys, thereby providing robust protection against basic impersonation attacks by adversaries. This capability relies on tamper-proof hardware and over-the-air rekeying to maintain signal integrity without requiring physical key updates. Proponents, including U.S. Department of Defense assessments, maintain that SAASM's encryption denies spoofers verifiable access to precise positioning data, preserving operational advantages in contested environments. Critics, however, question SAASM's sufficiency against integrated advanced threats from peer competitors like and , where high-power overwhelms receivers before can occur, effectively achieving denial-of-service without needing to breach . Unlike dedicated anti-jam technologies such as controlled reception pattern antennas, SAASM offers no inherent mitigation for , relying instead on the P(Y) code's higher chipping rate for limited processing gain that proves inadequate against modern systems capable of 100 or greater . A National Space Association report highlights this asymmetry, arguing that despite SAASM enhancements, U.S. GPS-dependent forces face superior regional from adversaries' ground-based emitters, as demonstrated in disruptions over the and since 2014. Debates intensify over potential exploits like meaconing—rebroadcasting delayed authentic signals—or sophisticated spoofing that synchronizes with genuine acquisitions to bypass initial verification thresholds, exploiting SAASM's reliance on post-acquisition . Operational critiques, such as 2010 U.S. incidents where SAASM-equipped receivers failed due to integration flaws in munitions, underscore implementation vulnerabilities that advanced adversaries could target through reverse-engineering captured hardware or cyber intrusions. While SAASM resists simple spoofing, analysts from think tanks like the Atlantic Council contend it falls short in multi-domain warfare, where adversaries combine , spoofing, and kinetic attacks, necessitating complementary assured PNT alternatives like inertial systems rather than over-reliance on GPS . The ongoing delay in full M-code adoption, which promises 60-fold anti-jam improvements via spot-beaming, further fuels arguments that SAASM represents an interim measure vulnerable to evolving threats.

References

  1. [1]
    [PDF] Global Positioning System (GPS) Selective Availability Anti-Spoofing ...
    SAASM is an enhanced GPS security architecture designed to provide over-the-air rekeying of GPS receivers in order to encrypt and decrypt the GPS signal. M-code ...
  2. [2]
    GPS Security with SAASM - Safran - Navigation & Timing
    One of the existing anti-spoofing technologies is the Selective Availability Anti-Spoofing Module (SAASM) available for the GPS constellation. A SAASM-enabled ...
  3. [3]
    Selective Availability Anti-Spoofing Module (SAASM)
    SAASM is used by military GP receivers to allow decryption of precision GPS observations and to help eliminate tampered satellite signals.
  4. [4]
    5.2 Enhanced GNSS Technologies - VectorNav
    While Selective Availability was deactivated in the early 2000s, the P(Y)-code remains encrypted to provide anti-spoofing (AS) capabilities. To decrypt the P(Y)- ...
  5. [5]
    SimSAAS - Classified testing of Y-Code & SAASM - Spirent Federal
    Military GPS receivers can use a Selective Availability Anti-Spoofing Module (SAASM) to enable decryption of precise positioning data. Selective Availability ...
  6. [6]
    Understanding the difference between anti-spoof and anti-jam
    Of course, this is only possible by using a GPS receiver that has a Selective Availability Anti-Spoofing Module (SAASM). SAASM receivers can track Y-code ...<|separator|>
  7. [7]
    [PDF] Plan for Development of an Enhanced Global Positioning System
    SAASM is the foundation for the future military GPS security architecture. SAASM provides three key advances. First, SAASM is compatible with the NSA's new key ...
  8. [8]
    [PDF] MicroGRAM GPS Receiver - BAE Systems
    At its core, the. MicroGRAM contains the Selective. Availability Anti-Spoofing Module. (SAASM). SAASM encapsulates all classified data and signal processing.
  9. [9]
    GPS SAASM - Frequency Electronics
    Selective Availability: Ensures that only authorized users with the correct decryption keys can access the precise GPS data, enhancing security. Benefits.
  10. [10]
    Can GPS be Trusted? Part 2 | Mercury Systems
    Oct 23, 2018 · Receivers that use P(Y)-code are called SAASM receivers (Selective Availability / Anti-Spoofing Module). It's the P(Y) code that provides the ...Missing: structure | Show results with:structure
  11. [11]
    What are Selective Availability Anti-Spoofing Modules (SAASM)?
    Aug 20, 2022 · These modules also use Selective Availability (SA) and anti-spoofing (AS) techniques to reduce the accuracy of civilian GPS receivers and ...
  12. [12]
    Satellite Navigation - Global Positioning System (GPS)
    The Global Positioning System, formally known as the Navstar Global Positioning System, was initiated as a joint civil/military technical program in 1973.
  13. [13]
    Global Positioning System Overview - GPS INFO - CNMOC
    Anti-spoofing (A-S) guards against fake transmissions of satellite data by encrypting the P-code to form the Y-code. SA was implemented on Block II at the ...
  14. [14]
    Selective Availability | GPS.gov
    Selective Availability (SA) was an intentional degradation of public GPS signals implemented for national security reasons.
  15. [15]
    [PDF] Why Convert to a SAASM-Based GPS Timing Receiver? - Aventas Inc.
    GPS devices in compliance with SAASM can receive and decrypt the P(Y) code (when keyed) which authenticates the signal originated from the GPS satel- lites.
  16. [16]
    [PDF] Why convert to a SAASM-based Global Positioning System?
    In 1998, the Joint Chiefs of Staff selected the Selective Availability. Anti-Spoofing Module (SAASM) as the security architecture to bring the Global.
  17. [17]
    Tamper-Proof GPS Receivers Installed in Smart Weapons
    Jun 1, 2002 · The SAASM module replaces the existing security chips that are installed in military GPS receivers to decrypt a classified access code.
  18. [18]
    [PDF] The Future of the Global Positioning System - DTIC
    First launch for the GPS III satellite was originally planned for FY09 with fully populated constellation by 2016/17; however, go-ahead delays and funding ...
  19. [19]
    Combat Survivor Evader Locator (CSEL) System - NAVAIR
    ... Selective Availability/Anti-spoofing Module (SAASM). Specifications. General ... Initial Operational Capability: January 2006. Full Operational Capability ...
  20. [20]
    Analysis of Potential Interference Issues Related to FCC Order 20-48
    As technology advanced, the GPS Joint Program Office began development of a Selective Availability Anti-Spoofing Module (SAASM) in the mid-1990s, which enabled ...Missing: history | Show results with:history
  21. [21]
    AGM-158 JASSM Program Developments - GlobalSecurity.org
    Jan 7, 2021 · In 1998, the Joint Chiefs of Staff selected the Selective Availability Anti-Spoofing Module ... 200 feet, and a fourth failed to detonate ...
  22. [22]
    Military GPS Policy Overview | PDF | Global Positioning System
    Sep 26, 2007 · Field only SAASM-based GPS User Equipment after 1 October 2002. Use GPS black keys no later than 1 October 2002. Cease fielding of non-SAASM- ...
  23. [23]
    [PDF] GAO-10-636 Global Positioning System: Challenges in Sustaining ...
    Sep 15, 2010 · Why GAO Did This Study. The Global Positioning System (GPS) provides positioning, navigation, and timing (PNT) data to users worldwide.<|separator|>
  24. [24]
    ONSITE PROGRAM - The Institute of Navigation
    ... (SAASM) program that has fielded almost 2 million SAASM-based receivers and attained Block II Electronic Protect Initial Operational Capability in 2014.
  25. [25]
    [PDF] A Security Analysis of GPS Signal Authentication.
    To restrict access to this signal, the P code gets encrypted to the P(Y) code by adding a secret and very long pseudo-random sequence W to the P code.
  26. [26]
    [PDF] gps characterization in cyberspace between vulnerability and geo ...
    Although the P-code is not classified, but it is encrypted to the. Y-code by Anti Spoofing (AS). Moreover, the Y-code is the summation of the P-code and the ...
  27. [27]
    GNSS Authentication and encryption - Navipedia - GSSC
    Feb 17, 2021 · Current examples of encrypted GNSS signals are GPS P(Y) code for military use, Galileo PRS or Galileo HAS (this latter will include providing ...Missing: details | Show results with:details
  28. [28]
    [PDF] 746 Test Squadron
    Oct 19, 2005 · – OverTheAir Rekeying (OTAR) capability: • This simplifies key distribution, storage, expiration and disposal issues and helps to maintain ...Missing: details | Show results with:details
  29. [29]
    [PDF] Over-the-Air Distribution (OTAD) Update - DTIC
    Apr 29, 2015 · - OTAD Next black key sent to user via the GPS navigation message. - OTAR Superset of OTAD key sent via the navigation message. • Receiver ...<|control11|><|separator|>
  30. [30]
    SAASM: Rockwell Collins' next generation GPS receiver design
    SAASM is a low-cost, common module for GPS applications, designed for easy integration and used in NavStrike, SSI, and GEM V receivers.
  31. [31]
    [PDF] Formally Verified Hardware Encapsulation Mechanism for Security ...
    The SAASM system architecture specifies separate red, yellow, and green program and data spaces for an application micro- processor, with a precise set of ...
  32. [32]
    Review and Analysis of the Selective Availability Anti-Spoofing ...
    This paper provides a brief history of the Selective Availability Anti-Spoofing Module program and a comprehensive review of the SAASM Card Integration Program ...
  33. [33]
    NavAssure® SAASM Dongle - Mayflower Communications
    The NavAssure® Dongle provides SAASM GPS receiver-based secure position location information to the Rifleman Radio as an external attachment.
  34. [34]
    [PDF] Integrating SAASM GPS and Inertial Navigation: What to Know
    The U.S. government's mandate that any military GPS system receiver be equipped with a Selective. Availability Anti-Spoofing Module (SAASM) microchip helps ...
  35. [35]
    Securing military GPS from spoofing and jamming vulnerabilities
    Nov 30, 2015 · We generally describe 'secure GPS' as military-encrypted GPS that uses military P(Y) code.” New terminology is starting to emerge from within ...Missing: mechanisms | Show results with:mechanisms
  36. [36]
    [PDF] MPETM-M Receiver - BAE Systems
    BAE Systems advances its proven heritage of Selective Availability Anti-. Spoofing Module (SAASM)-based products to M-Code, allowing soldiers to be more ...
  37. [37]
    NavGuard® 400 GPS Anti-Jam - Mayflower Communications
    NavGuard 420 is a high-performance, small, 4-channel anti-jam system, compatible with C/A, SAASM, and M-Code, and is an affordable SWaP-C alternative.
  38. [38]
    [PDF] Integrated GPS Anti-jam System (IGAS)
    IGAS is an integrated GPS and anti-jamming system for missile and munitions, providing accurate GPS navigation in a compact, cost-effective package.
  39. [39]
    Anti-jam systems: Which one works for you? - GPS World
    Jun 14, 2017 · Main features: “All three products protect the GPS L1 and L2 bands simultaneously, and are suitable for military (SAASM) receivers as well as ...
  40. [40]
    [PDF] Airborne SAASM Receiver - BAE Systems
    Specifically designed to meet small package requirements, the ASR provides GRAM-S performance in less than half the volume of a SEM-E receiver.<|separator|>
  41. [41]
    Miniature PLGR Engine-SAASM (MPE™-S) Type II GPS receiver
    Time accuracy. 100 nanoseconds. Position accuracy SDGPS: <2 meters CEP*. WAGE: <4 meters CEP*. PPS: <12 meters CEP*. Acquisition time TTFF <10 sec hot start ...
  42. [42]
    [PDF] RTK SAASM GPS receiver
    The RTK SAASM GPS receiver provides centimeter-level accuracy and SAASM security for unmanned aircraft, using RTK GPS and 20 cm 3D accuracy.
  43. [43]
    FRU-SAASM - Brandywine Communications
    FRU-SAASM. Frequency Reference Unit - Combination M-Code & SAASM Version ... Mean Time Between Failures, >70,000 hours. Physical. Dimensions, 1U Rack mount ...
  44. [44]
    Military GPS (DAGR) - BAE Systems
    Unlike commercial GPS receivers, DAGR provides secure, military SAASM-based GPS in the most reliable and proven handheld form available today.Missing: equipped | Show results with:equipped
  45. [45]
    Military GPS System - BAE Systems
    A small, low-power, G-hardened, SAASM-based GPS receiver with integrated five-channel anti-jam. Currently used on major weapons systems for precision- ...
  46. [46]
    DSCA 00-06 | Defense Security Cooperation Agency
    LOA Note Regarding Authorized Release and Transfer of Global Positioning System (GPS/PPS) Equipment (DSCA 00-06)
  47. [47]
    GPS SAASM Receivers - Mayflower Communications
    The Mayflower NavAssure® product line is offered through the United States Foreign Military Sales (FMS) program authorized by the Arms Export Control Act (AECA) ...
  48. [48]
    [PDF] Global Positioning System (GPS) Enterprise - DOT&E
    the Selective Availability Anti-Spoofing Module (SAASM). Mission Planning ... An apparent gap between MGUE Increment 1 functional capabilities and Military ...<|separator|>
  49. [49]
    [PDF] The Importance of a Military Receiver in a GPS-Contested ...
    The anti-spoof P(Y) code was developed to encrypt the military signal, a separate signal from the GPS satellite that commercial receivers cannot use. This ...<|separator|>
  50. [50]
    [PDF] America's Asymmetric Vulnerability to Navigation Warfare
    Jul 18, 2024 · The US is vulnerable because GPS has been surpassed by other systems, lacks a reliable backup, and is surpassed by China's Beidou in some areas.
  51. [51]
    Precision Guidance - BAE Systems
    Feb 13, 2025 · ... SAASM-based GPS receiver with integrated five-channel anti-jam. Currently used on major weapons systems for precision-guided artillery and bombs ...
  52. [52]
    GPS Compatibility Problem Sidelines Some U.S. Weapons Systems
    May 3, 2010 · Some 8,000 to 10,000 Selective Availability Anti-SpoofingModule (SAASM) GPS receivers deployed in a variety of weapon systems are having trouble ...
  53. [53]
    ITAR Controls on Military GNSS Receivers Updated
    Oct 17, 2016 · The State Department last week published its final rule that updates export controls on military GNSS receivers through the US Munitions List (USML).<|separator|>
  54. [54]
    Understand The ITAR - DDTC Public Portal - State Department
    The ITAR (22 CFR parts 120-130) governs the manufacture, export, and temporary import of defense articles, the furnishing of defense services, and brokering ...Missing: SAASM | Show results with:SAASM
  55. [55]
    Arms Sales Notification - Federal Register
    Nov 27, 2024 · The Embedded Global Positioning System/Inertial Navigation System (GPS/INS) (EGI) with Selective Availability Anti-Spoofing Module (SAASM)—or M- ...
  56. [56]
    DSCA 24-30 | Defense Security Cooperation Agency
    Oct 18, 2024 · This memorandum updates general policy and process guidance on Section 30 sales agreements, including moving this guidance from DSCA 24-04 Attachment B to SAMM ...Missing: adoption allied
  57. [57]
    Arms Sales Notification - Federal Register
    Dec 31, 2019 · ... GPS Receiver card with Selective Availability Anti-Spoofing Module (SAASM). The Force 524D is a 24-channel SAASM based GPS receiver with ...
  58. [58]
    A Better Way of Life for PPS Users ... GPS SAASM and P(Y) - DTIC
    This paper discusses the new GPS receiver technology being introduced to all U.S. Military Services and U.S. allies, now using standard PPS receivers.
  59. [59]
    (SBIR) Navy - Low Cost, Low Power, SAASM GPS Receiver with Up ...
    Aug 25, 2008 · The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), which controls the export and ...<|separator|>
  60. [60]
    22 CFR Part 121 -- The United States Munitions List - eCFR
    The range for rocket systems will be determined independently of any external factors such as operational restrictions, limitations imposed by telemetry, data ...
  61. [61]
    DSCA 24-71 | Defense Security Cooperation Agency
    Sep 23, 2024 · Defense Security Cooperation Agency Policy Memorandum 24-71, Guidance for Processing Letter of Offer and Acceptance in the Automated Export System.
  62. [62]
    [PDF] Overview of the GPS M Code Signal - MITRE Corporation
    The paper summarizes the history that led to GPS. Modernization with a new military signal on L1 and L2. After an overview of the M code signal design, the ...
  63. [63]
    [PDF] GPS MODERNIZATION DOD Continuing to Develop New Jam
    Jan 19, 2021 · The Air Force accepted the first GPS III satellite for operations in January of. 2020. ... GAO-21-145 GPS Modernization evaluation only on ...Missing: SAASM | Show results with:SAASM<|separator|>
  64. [64]
    Honeywell to Deliver First EGI with M-Code in 2023
    Honeywell is making it easy to upgrade its EGI system by swapping out the current Selective Availability Anti-Spoofing Module (SAASM) card with a new M-Code ...
  65. [65]
    GPS Source Now Offers Seamless Transition from SAASM to M-Code
    Oct 3, 2016 · The Enhanced D3 offers the unique ability to upgrade from SAASM to M-Code while integrating to the existing vehicle architecture and components.<|separator|>
  66. [66]
    [PDF] Global Positioning System (GPS) Enterprise
    In February. 2024, the M-code signal became globally available, giving U.S. and allied forces the ability to conduct testing of the M-code signal anywhere in ...Missing: rollout | Show results with:rollout
  67. [67]
    U.S. Army partnerships bring critical Assured PNT capabilities to ...
    May 14, 2025 · These precision-guided munitions improve projectile accuracy of conventional artillery munitions, decreasing delivery errors along with the ...
  68. [68]
    Successful demonstration of next-generation M-Code Increment 2 ...
    Oct 28, 2024 · This builds upon the flexibility offered by BAE Systems' current Selective Availability Anti-Spoofing Module (SAASM) and M-Code Increment 1 ...Missing: timeline | Show results with:timeline
  69. [69]
    BAE Systems Launches New Series of M-Code GPS Receivers
    Jun 4, 2025 · BAE Systems introduced new M-Code Global Positioning System receivers during the Joint Navigation Conference in Cincinnati, Ohio.Missing: rollout | Show results with:rollout
  70. [70]
    M-Code Program Eyes Operations - AFCEA International
    Oct 24, 2024 · Space Systems Command plans to reach fielding in its effort to enable military code in 2025.
  71. [71]
    Timeline for Troubled GPS Programs Continues to Grow
    Nov 12, 2024 · It all hinges on a signal called M-code: an encrypted signal intended to give military receivers better defense against jamming and increased ...
  72. [72]
    Seventh Lockheed Martin-Built GPS III Satellite Launches ...
    Dec 16, 2024 · M-Code is an advanced, new signal designed to improve anti-jamming and anti-spoofing, as well as increase secure access to military GPS signals ...
  73. [73]
    Positioning, Navigation & Timing – GPS III/IIIF | Lockheed Martin
    These upgrades have taken place under the GPS Control Segment (GCS) II contract. Notably, this ground control system has sustained a special capability called M ...Missing: ongoing | Show results with:ongoing
  74. [74]
    Space Segment | GPS.gov
    GPS III/IIIF (6 operational) · All Block IIF signals · 4th civil signal on L1 (L1C) · Enhanced signal reliability, accuracy, and integrity · No Selective ...
  75. [75]
    U. S. Space Force Field Commands successfully launch GPS III ...
    May 30, 2025 · The GPS III satellite, equipped with M-code technology, provides the warfighter with a capability that is three-times more accurate, and eight- ...Missing: IIIF features
  76. [76]
    Anti-Jamming GPS Upgrades Coming This Year
    Apr 29, 2025 · The GPS III birds take full advantage of M-code, a more robust, encrypted, jam-resistant signal for military use. While other GPS satellites ...
  77. [77]
    Space Force Finally Accepts New GPS Operating System
    Jul 16, 2025 · The update is key to enabling enhancements like anti-jamming, improved accuracy, and secure geolocation using M-Code. It has been a long and ...
  78. [78]
    Lockheed Martin Tapped for Two More GPS IIIF Space Force ...
    May 30, 2025 · GPS IIIF enhances navigation capabilities with 60x anti-jamming resistance, new search and rescue functions, and a fully digital payload; SV08, ...
  79. [79]
    [PDF] GAO-24-106841, GPS MODERNIZATION: Delays Continue in ...
    Sep 9, 2024 · M-code is a stronger, encrypted, military-specific GPS signal designed to meet military PNT information needs.Missing: rollout | Show results with:rollout
  80. [80]
    GPS Modernization: Delays Continue in Delivering More Secure ...
    Sep 9, 2024 · DOD has been working for years to upgrade GPS with a military-specific signal known as M-code that resists interference or jamming.
  81. [81]
    Jam-resistant GPS elusive as M-code delays pile up: GAO
    Sep 9, 2024 · “Many of the programs that are part of the GPS modernization effort had significant development challenges that resulted in cost overruns and ...
  82. [82]
    Combating jamming and spoofing - GPS World
    May 13, 2024 · Jamming and spoofing continue to be the key challenges to military use of GNSS. While the production and adoption of M-Code receivers is delayed.
  83. [83]
    New military code about to board 700+ platforms - GPS World
    Apr 9, 2019 · Our DIGAR AJ technology enhances the performance with fixed reception pattern antenna (FRPA), CRPA and is compatible with all PPS waveforms.
  84. [84]
    BAE Systems Status Update for M-Code User Equipment
    We provide a status update for our M-Code product line and anti-jam antenna electronics, including a progress report for the development of our NavGuide™ GPS ...Missing: upgrades | Show results with:upgrades<|separator|>
  85. [85]
    Timeline for Troubled GPS Programs Continues to Grow
    the Army planning to field platforms in fiscal years 2024 and 2025 and the Navy to ...Missing: rollout | Show results with:rollout
  86. [86]
    MARINE CORPS MILITARY GLOBAL POSITIONING SYSTEM (GPS ...
    Oct 4, 2018 · Positioning, navigation, and timing capabilities provided by SPS GPS devices may not be reliable, or available during conflict.
  87. [87]
    Spoofs, Proofs & Jamming - Inside GNSS
    Sep 3, 2012 · Scott 2011A), illustrates how the location of a small, 200-milliwatt ... Are receivers with a Selective Availability/Anti-Spoofing Module ...
  88. [88]
    Key management for military GPS receivers
    Sep 22, 2014 · The SV (space vehicle - aka the satellite) transmits an encrypted P(Y) code. The encryption key, called Cryptovariable Daily Key ( CVd ) changes ...
  89. [89]
    None
    ### Summary of Vulnerabilities and Exploits in GPS Receivers
  90. [90]
    Defense Dept. Studying Options To Lower Cost of GPS Receivers
    May 1, 2004 · Experts attribute the high cost of military receivers to the anti-tamper chip, called the GPS selective availability anti-spoofing module. ...
  91. [91]
    Air Force Working Through GPS Receiver Problems - SpaceNews
    May 7, 2010 · The problem was isolated to a specific type of GPS receiver known as the Selective Availability Anti-Spoofing Module (SAASM) deployed in at ...Missing: initial | Show results with:initial
  92. [92]
    DoD GPS cost savings program to be continued by Rockwell Collins
    The low-cost GPS program reduced the size, weight, power, and cost of GPS devices. So far, the program produced an estimated $100 million in savings for the ...
  93. [93]
    The Growing Threat of GPS Jamming and Navigation Warfare
    Apr 21, 2025 · The Growing Threat: GNSS Vulnerabilities in Modern Warfare. GNSS signals face multiple vulnerabilities that adversaries are actively exploiting.<|separator|>
  94. [94]
    With GPS, failure is not an option. - Atlantic Council
    Oct 18, 2016 · Those newer, more robust, Y-code sets are of the Selective Availability Anti-Spoofing Module (SAASM, or sazum) generation or later, and the ...Missing: weaknesses | Show results with:weaknesses