Project 25

<h2 id="suite-of-standards-overview">Suite of standards overview</h2>
<h3>History</h3>
Public safety radios have been upgraded from <a href="/facts/Analog_signal/xDbb4uB5">analog</a> <a href="/facts/Frequency_modulation/qIExDdtv">FM</a> to <a href="/facts/Digital_data/JChckAvr">digital</a> since the 1990s because of an increased use of data on radio systems for such features as GPS location, <a href="/facts/Trunked_radio_system/wySDmdrY">trunking</a>, text messaging, metering, and encryption.
Various user protocols and different <a href="/facts/Public_security/qrjPmFHH">public safety</a> <a href="/facts/Radio_spectrum/AP2frA1C">radio spectrum</a> made it difficult for Public Safety agencies to achieve interoperability and widespread acceptance. However, lessons learned during disasters the United States faced in the past decades have forced agencies to assess their requirements during a disaster when basic infrastructure has failed. To meet the growing demands of public safety digital radio communication, the United States <a href="/facts/Federal_Communications_Commission/Ueghz8W0">Federal Communications Commission</a> (FCC) at the direction of the <a href="/facts/United_States_Congress/mJlU46K7">United States Congress</a> initiated a 1988 inquiry for recommendations from users and manufacturers to improve existing communication systems.<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a><a class="footnote-ref" id="fnref:3" href="#fn:3">3</a> Based on the recommendations, to find solutions that best serve the needs of public safety management, in October 1989 APCO Project 25 came into existence in a coalition with:<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a><a class="footnote-ref" id="fnref:5" href="#fn:5">5</a>

<ul><li><a href="/facts/Association_of_Public-Safety_Communications_Officials-International/7a4ggICD">Association of Public-Safety Communications Officials-International</a> (APCO)</li>
<li>National Association of State Telecommunications Directors (NASTD)<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a></li>
<li><a href="/facts/National_Telecommunications_and_Information_Administration/NU3jouvb">National Telecommunications and Information Administration</a> (NTIA)</li>
<li><a href="/facts/National_Communications_System/XMaKIdnS">National Communications System</a> (NCS)</li>
<li><a href="/facts/National_Security_Agency/Sg6MGV1o">National Security Agency</a> (NSA)</li>
<li><a href="/facts/United_States_Department_of_Defense/dWAvf7e3">Department of Defense</a> (DoD)</li></ul>
A steering committee consisting of representatives from the above-mentioned agencies along with FPIC (<a href="/facts/Department_of_Homeland_Security/jwz5gLfa">Department of Homeland Security</a> Federal Partnership for Interoperable Communication), <a href="/facts/United_States_Coast_Guard/6d7SWTP9">Coast Guard</a> and the <a href="/facts/United_States_Department_of_Commerce/3sch0DLr">Department of Commerce</a>'s <a href="/facts/National_Institute_of_Standards_and_Technology/gr9Fnh85">National Institute of Standards and Technology</a> (NIST), Office of Law Enforcement Standards was established to decide the priorities and scope of technical development of P25.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a>

<h3>Introduction</h3>
Interoperable emergency communication is integral to initial response, public health, community safety, national security and economic stability. Of all the problems experienced during disaster events, one of the most serious is poor communication due to lack of appropriate and efficient means to collect, process, and transmit important information in a timely fashion. In some cases, radio communication systems are incompatible and inoperable not just within a jurisdiction but within departments or agencies in the same community.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a> Non-operability occurs due to use of outdated equipment, limited availability of radio frequencies, isolated or independent planning, lack of coordination, and cooperation, between agencies, community priorities competing for resources, funding and ownership, and control of communications systems.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a> Recognizing and understanding this need, Project 25 (P25) was initiated collaboratively by public safety agencies and manufacturers to address the issue with <a href="/facts/Emergency_communication_system/rAHkcxAh">emergency communication systems</a>. P25 is a collaborative project to ensure that <a href="/facts/Two-way_radio/e6JKFtdo">two-way radios</a> are interoperable. The goal of P25 is to enable public safety responders to communicate with each other and, thus, achieve enhanced coordination, timely response, and efficient and effective use of communications equipment.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a>
P25 was established to address the need for common digital public safety radio communications standards for first-responders and homeland security/emergency response professionals. The <a href="/facts/Telecommunications_Industry_Association/2UlrgpAx">Telecommunications Industry Association</a>'s <a href="http://tiaonline.org/all-standards/committees/tr-8">TR-8</a> engineering committee facilitates such work through its role as an ANSI-accredited <a href="/facts/Standards_organization/8o7wGeYg">standards development organization</a> (SDO) and has published the P25 suite of standards as the TIA-102 series of documents, which now include 49 separate parts on Land Mobile Radio and TDMA implementations of the technology for public safety.<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a>

<blockquote>Project 25 (P25) is a set of standards produced through the joint efforts of the <a href="/facts/Association_of_Public_Safety_Communications_Officials_International/7a4ggICD">Association of Public Safety Communications Officials International</a> (APCO), the National Association of State Telecommunications Directors (NASTD), selected federal agencies and the National Communications System (NCS), and standardized under the <a href="/facts/Telecommunications_Industry_Association/2UlrgpAx">Telecommunications Industry Association</a> (TIA)... The P25 suite of standards involves digital Land Mobile Radio (<a href="/facts/Land_Mobile_Radio_System/mkV1JFFr">LMR</a>) services for local, state/provincial and national (federal) public safety organizations and agencies...
P25 is applicable to LMR equipment authorized or licensed, in the U.S., under NTIA or FCC rules and regulations.

Although developed primarily for North American public safety services, P25 technology and products are not limited to public safety alone and have also been selected and deployed in other private system application, worldwide.<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a></blockquote>
P25-compliant systems are being increasingly adopted and deployed throughout the United States, as well as other countries. Radios can communicate in <a href="/facts/Analog_signal/xDbb4uB5">analog</a> mode with legacy radios, and in either <a href="/facts/Digital_signal_(signal_processing)/bCtTHxre">digital</a> or analog mode with other P25 radios. Additionally, the deployment of P25-compliant systems will allow for a high degree of equipment interoperability and compatibility.
P25 standards use the proprietary <a href="/facts/Improved_Multi-Band_Excitation/69xJgVlz">Improved Multi-Band Excitation</a> (IMBE) and <a href="/facts/Advanced_Multi-Band_Excitation/69xJgVlz">Advanced Multi-Band Excitation</a> (AMBE+2) voice codecs which were designed by Digital Voice Systems, Inc. to encode/decode the analog audio signals. It is rumored that the licensing cost for the voice-codecs that are used in P25 standard devices is the main reason that the cost of P25 compatible devices is so high.<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>
P25 may be used in "talk around" mode without any intervening equipment between two radios, in conventional mode where two radios communicate through a repeater or base station without trunking or in a <a href="/facts/Trunked_Radio_Systems/wySDmdrY">trunked</a> mode where traffic is automatically assigned to one or more voice channels by a <a href="/facts/Repeater/JTkWvTEP">Repeater</a> or Base Station.
The protocol supports the use of <a href="/facts/Data_Encryption_Standard/STfBjTGb">Data Encryption Standard</a> (DES) encryption (56 bit), 2-key <a href="/facts/Triple-DES/sgzSD50P">Triple-DES</a> encryption, three-key <a href="/facts/Triple-DES/sgzSD50P">Triple-DES</a> encryption, <a href="/facts/Advanced_Encryption_Standard/HdXGBY2Q">Advanced Encryption Standard</a> (AES) encryption at up to 256 bits keylength, <a href="/facts/RC4/HAR5kL0T">RC4</a> (<a href="/facts/40-bit_encryption/beKmt3n2">40 bits</a>, sold by Motorola as Advanced Digital Privacy), or no encryption.
The protocol also supports the ACCORDION 1.3, <a href="/facts/BATON/DVzcQCdW">BATON</a>, <a href="/facts/Firefly_(protocol)/AsDYDz2C">Firefly</a>, MAYFLY and <a href="/facts/SAVILLE/drc4XgJK">SAVILLE</a> <a href="/facts/Type_1_encryption/uKCkqR8E">Type 1</a> ciphers.

<h3>P25 open interfaces</h3>
P25's Suite of Standards specify eight open interfaces between the various components of a land mobile radio system. These interfaces are:

<ul><li>Common Air Interface (CAI) – standard specifies the type and content of signals transmitted by compliant radios. One radio using CAI should be able to communicate with any other CAI radio, regardless of manufacturer</li>
<li>Subscriber Data Peripheral Interface – standard specifies the port through which mobiles and portables can connect to laptops or data networks</li>
<li>Fixed Station Interface – standard specifies a set of mandatory messages supporting digital voice, data, encryption and telephone interconnect necessary for communication between a Fixed Station and P25 RF Subsystem</li>
<li>Console Subsystem Interface – standard specifies the basic messaging to interface a console subsystem to a P25 RF Subsystem</li>
<li>Network Management Interface – standard specifies a single network management scheme which will allow all network elements of the RF subsystem to be managed</li>
<li>Data Network Interface – standard specifies the RF Subsystem's connections to computers, data networks, or external data sources</li>
<li>Telephone Interconnect Interface – standard specifies the interface to Public Switched Telephone Network (PSTN) supporting both analog and ISDN telephone interfaces.</li>
<li>Inter RF Subsystem Interface (<a href="/facts/P25_ISSI/tbskx7vS">ISSI</a>) – standard specifies the interface between RF subsystems which will allow them to be connected into wide area networks</li></ul>
<h3>P25 phases</h3>

P25-compliant technology has been deployed over two main phases with future phases yet to be finalized.

<h4>Phase 1</h4>
Phase 1 radio systems operate in 12.5 kHz digital mode using a single user per channel access method. Phase 1 radios use Continuous 4 level <a href="/facts/FM_broadcasting/TpKl3FJv">FM</a> (C4FM) modulation—a special type of 4<a href="/facts/Frequency-shift_keying/Bp1jJDPX">FSK</a> modulation<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a>—for digital transmissions at 4,800 <a href="/facts/Baud/uCsmXrdT">baud</a> and 2 <a href="/facts/Bit/S972NSaD">bits</a> per symbol, yielding 9,600 bits per second total channel throughput. Of this 9,600, 4,400 is voice data generated by the <a href="/facts/Improved_multi-band_excitation/69xJgVlz">IMBE</a> codec, 2,800 is forward error correction, and 2,400 is signalling and other control functions. Receivers designed for the C4FM standard can also demodulate the "Compatible quadrature <a href="/facts/Phase_shift_keying/TFnpYe64">phase shift keying</a>" (CQPSK) standard, as the parameters of the CQPSK signal were chosen to yield the same signal <a href="/facts/Absolute_deviation/F7cqnhtF">deviation</a> at symbol time as C4FM. Phase 1 uses the <a href="/facts/Improved_multi-band_excitation/69xJgVlz">IMBE</a> voice codec.
These systems involve standardized service and facility specifications, ensuring that any manufacturers' compliant subscriber radio has access to the services described in such specifications. Abilities include <a href="/facts/Backward_compatibility/FbHFBu5y">backward compatibility</a> and interoperability with other systems, across system boundaries, and regardless of system infrastructure. In addition, the P25 suite of standards provides an open interface to the radio frequency (RF) subsystem to facilitate interlinking of different vendors' systems.

<h4>Phase 2</h4>
To improve spectrum use, P25 Phase 2 was developed for trunking systems using a 2-slot <a href="/facts/Time-division_multiple_access/ue5UzN7B">TDMA</a> scheme and is now required for all new trunking systems in the 700 MHz band.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a> Phase 2 uses the <a href="/facts/Advanced_Multi-Band_Excitation/69xJgVlz">AMBE+2</a> voice codec to reduce the needed bitrate so that one voice channel will only require 6,000 bits per second (including error correction and signalling). Phase 2 is not backwards compatible with Phase 1 (due to the TDMA operation), although multi-mode TDMA radios and systems are capable of operating in Phase 1 mode when required, if enabled. A subscriber radio cannot use TDMA transmission without a synchronization source; therefore direct radio to radio communication resorts to conventional FDMA digital operation. Multi-band subscriber radios can also operate on narrow-band FM as a lowest common denominator between almost any two way radios. This makes analog narrow-band FM the de facto "interoperability" mode for some time.
Originally the implementation of Phase 2 was planned to split the 12.5 kHz channel into two 6.25 kHz slots, or Frequency-Division Multiple Access (FDMA). However it proved more advantageous to use existing 12.5 kHz frequency allocations in Time Division Multiple Access (TDMA) mode for a number of reasons. It allowed subscriber radios to save battery life by only transmitting half the time which also yields the ability for the subscriber radio to listen and respond to system requests between transmissions.
Phase 2 is what is known as 6.25 kHz "bandwidth equivalent" which satisfies an FCC requirement for voice transmissions to occupy less bandwidth. Voice traffic on a Phase 2 system transmits with the full 12.5 kHz per frequency allocation, as a Phase 1 system does, however it does so at a faster data rate of 12 kbit/s allowing two simultaneous voice transmissions. As such subscriber radios also transmit with the full 12.5 kHz, but in an on/off repeating fashion resulting in half the transmission and thus an equivalent of 6.25 kHz per each radio. This is accomplished using the AMBE voice coder that uses half the rate of the Phase 1 IMBE voice coders.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>

<h4>Beyond Phase 2</h4>
From 2000 to 2009, the <a href="/facts/European_Telecommunications_Standards_Institute/8rJbbhPg">European Telecommunications Standards Institute</a> (ETSI) and TIA were working collaboratively on the Public Safety Partnership Project or Project MESA (Mobility for Emergency and Safety Applications),<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a> which sought to define a unified set of requirements for a next-generation aeronautical and terrestrial digital wideband/broadband radio standard that could be used to transmit and receive voice, video, and high-speed data in wide-area, multiple-agency networks deployed by public safety agencies.<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a><a class="footnote-ref" id="fnref:19" href="#fn:19">19</a>
The final functional and technical requirements have been released by ETSI<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a> and were expected to shape the next phases of American Project 25 and European DMR, <a href="/facts/DPMR/NB1I73Nj">dPMR</a>, and TETRA, but no interest from the industry followed, since the requirements could not be met by available commercial off-the-shelf technology, and the project was closed in 2010.
During the <a href="/facts/United_States_2008_wireless_spectrum_auction/r0spx5lX">United States 2008 wireless spectrum auction</a>, the FCC allocated 20 MHz of the 700 MHz <a href="/facts/UHF/S6XDUaDY">UHF</a> radio band spectrum <a href="/facts/Digital_television_transition_in_the_United_States/fbs2Tp7z">freed in the digital TV transition</a> to public safety networks. The FCC expects providers to employ <a href="/facts/Long_Term_Evolution/72QhwXHT">LTE</a> for high-speed data and video applications.<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>

<h2 id="conventional-implementation">Conventional implementation</h2>
P25 systems do not have to resort to using in band signaling such as <a href="/facts/Continuous_Tone-Coded_Squelch_System/8aoQT8Sj">Continuous Tone-Coded Squelch System</a> (CTCSS) tone or <a href="/facts/Digital-Coded_Squelch/wuhD7r3T">Digital-Coded Squelch</a> (DCS) codes for access control. Instead they use what is called a Network Access Code (NAC) which is included outside of the digital voice frame. This is a 12-bit code that prefixes every packet of data sent, including those carrying voice transmissions.
The NAC is a feature similar to CTCSS or DCS for analog radios. That is, radios can be programmed to only pass audio when receiving the correct NAC. NACs are programmed as a three-hexadecimal-digit code that is transmitted along with the digital signal being transmitted.
Since the NAC is a three-hexadecimal-digit number (12 bits), there are 4,096 possible NACs for programming, far more than all analog methods combined.
Three of the possible NACs have special functions:

<ul><li>0x293 ($293) – the default NAC</li>
<li>0xf7e ($F7E) – a receiver set for this NAC will pass audio on any decoded signal received</li>
<li>0xf7f ($F7F) – a repeater receiver set for this NAC will allow all incoming decoded signals and the repeater transmitter will retransmit the received NAC.</li></ul>
<h2 id="adoption">Adoption</h2>
Adoption of these standards has been slowed by budget problems in the US; however, funding for communications upgrades from the <a href="/facts/Department_of_Homeland_Security/jwz5gLfa">Department of Homeland Security</a> usually requires migrating to Project 25. It is also being used in other countries worldwide including Australia, New Zealand, Brazil,<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a> Canada, India and Russia.<a class="footnote-ref" id="fnref:23" href="#fn:23">23</a> As of mid-2004 there were 660 networks with P25 deployed in 54 countries.<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a> At the same time, in 2005, the European <a href="/facts/Terrestrial_Trunked_Radio/15j9PvnV">Terrestrial Trunked Radio</a> (TETRA) was deployed in sixty countries, and it is the preferred choice in Europe, China, and other countries.<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a> This was largely based on TETRA systems being many times cheaper than P25 systems ($900 vs $6,000 for a radio)<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a> at the time. However P25 radio prices are rapidly approaching parity with TETRA radio prices through increased competition in the P25 market. The majority of P25 networks are based in Northern America where it has the advantage that a P25 system has the same coverage and frequency bandwidth as the earlier analog systems that were in use so that channels can be easily upgraded one by one.<a class="footnote-ref" id="fnref:27" href="#fn:27">27</a> Some P25 networks also allow intelligent migration from the analog radios to digital radios operating within the same network. Both P25 and TETRA can offer varying degrees of functionality, depending on available radio spectrum, terrain and project budget.
While interoperability is a major goal of P25, many P25 features present interoperability challenges. In theory, all P25 compliant equipment is interoperable. In practice, interoperable communications isn't achievable without effective governance, standardized operating procedures, effective training and exercises, and inter-jurisdictional coordination. The difficulties inherent in developing P25 networks using features such as digital voice, encryption, or trunking sometimes result in feature-backlash and organizational retreat to minimal "feature-free" P25 implementations which fulfill the letter of any Project 25 migration requirement without realizing the benefits thereof. Additionally, while not a technical issue per se, frictions often result from the unwieldy bureaucratic inter-agency processes that tend to develop in order to coordinate interoperability decisions.

<h3>Naming of P25 technology in regions</h3>
<ul><li><a href="/facts/Government_radio_networks_in_Australia/nPk1IlFu">Statewide P25 systems in Australia</a> were deployed using the name Government Radio Network (GRN) in <a href="/facts/New_South_Wales/aW7eJXSS">New South Wales</a>, <a href="/facts/South_Australia/R7UdxV97">South Australia</a>, and <a href="/facts/Tasmania/q3dubPTt">Tasmania</a>; Government Wireless Network (GWN) in <a href="/facts/Queensland/lXBlIeY3">Queensland</a>; Territory Radio Network (TRN) in the <a href="/facts/Australian_Capital_Territory/wvCnG3y7">Australian Capital Territory</a>; and Melbourne Metropolitan Radio (MMR) and Rural Mobile Radio (RMR) in <a href="/facts/Victoria_(state)/76P2nqtz">Victoria</a>.<a class="footnote-ref" id="fnref:28" href="#fn:28">28</a><a class="footnote-ref" id="fnref:29" href="#fn:29">29</a><a class="footnote-ref" id="fnref:30" href="#fn:30">30</a><a class="footnote-ref" id="fnref:31" href="#fn:31">31</a> In New South Wales, the GRN is now called the Public Safety Network (PSN).<a class="footnote-ref" id="fnref:32" href="#fn:32">32</a></li></ul>
<h2 id="project-25-compliance-assessment-program-p25-cap">Project 25 Compliance Assessment Program (P25 CAP)</h2>
The United States <a href="/facts/DHS/jwz5gLfa">DHS</a>'s Project 25 Compliance Assessment Program (P25 CAP)<a class="footnote-ref" id="fnref:33" href="#fn:33">33</a> aims for interoperability among different vendors by testing to P25 Standards. P25 CAP, a voluntary program, allows suppliers to publicly attest to their products' compliance.<a class="footnote-ref" id="fnref:34" href="#fn:34">34</a>
Independent, accredited labs test vendor's P25 radios for compliance to P25 Standards, derived from <a href="/facts/Telecommunications_Industry_Association/2UlrgpAx">TIA-102</a> Standards and following TIA-TR8 testing procedures. Only approved products<a class="footnote-ref" id="fnref:35" href="#fn:35">35</a> may be purchased using US federal grant dollars.<a class="footnote-ref" id="fnref:36" href="#fn:36">36</a> Generally, non-approved products should not be trusted to be meet P25 standards for performance, conformance, and interoperability.
P25 product labeling varies. "P25" and "P25 compliant" mean nothing while high standards apply for a vendor to claim a product is "P25 CAP compliant" or "P25 compliant with the Statement of Requirements (P25 SOR)"<a class="footnote-ref" id="fnref:37" href="#fn:37">37</a>

<h2 id="security-flaws">Security flaws</h2>
<h3>OP25 Project—Encryption flaws in DES-OFB and ADP ciphers</h3>
At the Securecomm 2011 conference in London, security researcher Steve Glass presented a paper, written by himself and co-author Matt Ames, that explained how DES-OFB and Motorola's proprietary ADP (RC4 based) ciphers were vulnerable to brute force key recovery.<a class="footnote-ref" id="fnref:38" href="#fn:38">38</a> This research was the result of the OP25 project<a class="footnote-ref" id="fnref:39" href="#fn:39">39</a> which uses <a href="/facts/GNU_Radio/FslKwfjI">GNU Radio</a><a class="footnote-ref" id="fnref:40" href="#fn:40">40</a> and the Ettus <a href="/facts/Universal_Software_Radio_Peripheral/Nldbmq5S">Universal Software Radio Peripheral</a> (USRP)<a class="footnote-ref" id="fnref:41" href="#fn:41">41</a> to implement an open source P25 <a href="/facts/Packet_sniffer/mFQP7gWB">packet sniffer</a> and analyzer. The OP25 project was founded by Steve Glass in early 2008 while he was performing research into wireless networks as part of his PhD thesis.
The paper is available for download from the <a href="/facts/NICTA/VAaLnlaa">NICTA</a> website.<a class="footnote-ref" id="fnref:42" href="#fn:42">42</a>

<h3>University of Pennsylvania research</h3>
In 2011, the <a href="/facts/Wall_Street_Journal/9Pkf2cYK">Wall Street Journal</a> published an article describing research into security flaws of the system, including a user interface that makes it difficult for users to recognize when transceivers are operating in secure mode.<a class="footnote-ref" id="fnref:43" href="#fn:43">43</a> According to the article, "(R)esearchers from the <a href="/facts/University_of_Pennsylvania/LBBBULox">University of Pennsylvania</a> overheard conversations that included descriptions of <a href="/facts/Undercover_agents/3rBdHVBs">undercover agents</a> and <a href="/facts/Informant/TUMMRnHR">confidential informants</a>, plans for forthcoming arrests and information on the technology used in surveillance operations." The researchers found that the messages sent over the radios are sent in segments, and blocking just a portion of these segments can result in the entire message being jammed. "Their research also shows that the radios can be effectively jammed (single radio, short range) using a highly modified pink electronic child's toy and that the standard used by the radios 'provides a convenient means for an attacker' to continuously track the location of a radio's user. With other systems, jammers have to expend a lot of power to block communications, but the P25 radios allow jamming at relatively low power, enabling the researchers to prevent reception using a $30 toy pager designed for pre-teens."
The report was presented at the 20th <a href="/facts/USENIX/2wz6aQwq">USENIX</a> Security Symposium in <a href="/facts/San_Francisco/cb9l7hbC">San Francisco</a> in August 2011.<a class="footnote-ref" id="fnref:44" href="#fn:44">44</a> The report noted a number of security flaws in the Project 25 system, some specific to the way it has been implemented and some inherent in the security design.

<h4>Encryption lapses</h4>
The report did not find any breaks in the P25 encryption; however, they observed large amounts of sensitive traffic being sent in the clear due to implementations problems. They found switch markings for secure and clear modes difficult to distinguish (∅ vs. o). This is exacerbated by the fact that P25 radios when set to secure mode continue to operate without issuing a warning if another party switches to clear mode. In addition, the report authors said many P25 systems change keys too often, increasing the risk that an individual radio on a net may not be properly keyed, forcing all users on the net to transmit in the clear to maintain communications with that radio.

<h4>Jamming vulnerability</h4>
One design choice was to use lower levels of error correction for portions of the encoded voice data that are deemed less critical for intelligibility. As a result, bit errors may be expected in typical transmissions, and while harmless for voice communication, the presence of such errors force the use of <a href="/facts/Stream_cipher/BxU0aWmJ">stream ciphers</a>, which can tolerate bit errors, and prevents the use of a standard technique, <a href="/facts/Message_authentication_code/mXxCP5Yl">message authentication codes</a> (MACs), to protect message integrity from <a href="/facts/Stream_cipher_attack/AMMpWTHz">stream cipher attacks</a>. The varying levels of error correction are implemented by breaking P25 message frames into subframes. This allows an attacker to jam entire messages by transmitting only during certain short subframes that are critical to reception of the entire frame. As a result, an attacker can effectively jam Project 25 signals with average power levels much lower than the power levels used for communication. Such attacks can be targeted at encrypted transmissions only, forcing users to transmit in the clear.
Because Project 25 radios are designed to work in existing two-way radio frequency channels, they cannot use <a href="/facts/Spread_spectrum/0NKdJX1S">spread spectrum</a> modulation, which is inherently jam-resistant. An optimal spread spectrum system can require an effective jammer to use 1,000 times as much power (30 dB more) as the individual communicators. According to the report, a P25 jammer could effectively operate at 1/25th the power (14 dB less) than the communicating radios. The authors developed a proof-of-concept jammer using a Texas Instruments CC1110 single chip radio, found in an inexpensive toy.<a class="footnote-ref" id="fnref:45" href="#fn:45">45</a>

<h4>Traffic analysis and active tracking</h4>
Certain metadata fields in the Project 25 protocol are not encrypted, allowing an attacker to perform <a href="/facts/Traffic_analysis/ReJ8of8l">traffic analysis</a> to identify users. Because Project 25 radios respond to bad data packets addressed to them with a retransmission request, an attacker can deliberately send bad packets forcing a specific radio to transmit even if the user is attempting to maintain <a href="/facts/Radio_silence/WbVDKChl">radio silence</a>. Such tracking by authorized users is considered a feature of P25, referred to as "presence".<a class="footnote-ref" id="fnref:46" href="#fn:46">46</a>
The report's authors concluded by saying "It is reasonable to wonder why this protocol, which was developed over many years and is used for sensitive and critical applications, is so difficult to use and so vulnerable to attack." The authors separately issued a set of recommendations for P25 users to mitigate some of the problems found.<a class="footnote-ref" id="fnref:47" href="#fn:47">47</a> These include disabling the secure/clear switch, using Network Access Codes to segregate clear and encrypted traffic, and compensating for the unreliability of P25 over-the-air rekeying by extending key life.

<h2 id="comparison-between-p25-and-tetra">Comparison between P25 and TETRA</h2>
P25 and TETRA are used in more than 53 countries worldwide for both public safety and private sector radio networks. There are some differences in features and capacities:<a class="footnote-ref" id="fnref:48" href="#fn:48">48</a><a class="footnote-ref" id="fnref:49" href="#fn:49">49</a><a class="footnote-ref" id="fnref:50" href="#fn:50">50</a>

<ul><li>TETRA is optimized for high population density areas, and has spectral efficiency of 4 time slots in 25 kHz. (Four communications channels per 25 kHz channel, an efficient use of spectrum). It supports full-duplex voice communication, data, and messaging. It does not provide simulcast.</li>
<li>P25 is optimized for wider area coverage with low population density, and also supports simulcast. It is, however, limited with respect to data support. There is a major subdivision within P25 radio systems: Phase I P25 operates analogue, digital, or mixed mode in a single 12.5 kHz channel. Phase II uses a 2-timeslot TDMA structure in each 12.5 kHz channel.</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/APCO-16/k4unjcTW">APCO-16</a>, an earlier standard that specified trunking formats and radio operation</li>
<li><a href="/facts/Digital_Audio_Broadcasting/9GNkj4kL">Digital Audio Broadcasting</a></li>
<li><a href="/facts/Digital_terrestrial_television/9UoV0vV1">Digital terrestrial television</a></li>
<li><a href="/facts/Government_radio_networks_in_Australia/nPk1IlFu">Government radio networks in Australia</a>, examples deployment of P25 technology</li>
<li><a href="/facts/NXDN/F7PpBaTS">NXDN</a>, a two-way digital radio standard with similar characteristics (Optional TDMA)</li>
<li><a href="/facts/Terrestrial_Trunked_Radio/15j9PvnV">Terrestrial Trunked Radio</a>, TETRA, the European(EU) standard equivalent to P25</li></ul>
<h2 id="notes">Notes</h2>

<h2 id="external-links">External links</h2>
<ul><li><a href="https://www.project25.org/">Official website</a></li>
<li><a href="https://web.archive.org/web/20111019223730/http://www.tiaonline.org/standards/technology/project_25/index.cfm">P25 Overview</a> TIA Standards Development Activities for Public Safety</li>
<li><a href="https://web.archive.org/web/20110223005820/http://www.apco911.org/frequency/project25.php">"AFC - Public Safety Radio Spectrum Project 25 (P25)"</a>. Archived from <a href="http://www.apco911.org/frequency/project25.php">the original</a> on 2011-02-23. Retrieved 2025-04-06.</li>
<li><a href="https://web.archive.org/web/19980429050525/http://www.apco.ca:80/">"APCO Canada"</a>. Archived from <a href="http://www.apco.ca/">the original</a> on 1998-04-29. Retrieved 2025-04-06.</li>
<li><a href="https://web.archive.org/web/20050128161407/http://dvsinc.com:80/papers/p25_training_guide.pdf">"P25 Radio Systems"</a> (PDF). Archived from <a href="http://www.dvsinc.com/papers/p25_training_guide.pdf">the original</a> (PDF) on 2005-01-28.</li>
<li><a href="https://valid8.com/solutions/p25-issi-cssi-conformance">"Valid8's P25 ISSI CSSI Protocol Conformance Test Suites provide a convenient method to test the dispatch console and the RFSS on the ISSI and CSSI interfaces according to the TIA and CAP standards"</a>. valid8.com. Retrieved 2025-04-06.</li>
<li><a href="https://web.archive.org/web/20170611161725/http://www.dvsinc.com/prj25.htm">"DVSI P25 Page"</a>. Archived from <a href="http://www.dvsinc.com/prj25.htm">the original</a> on 2017-06-11. Retrieved 2025-04-06.</li>
<li><a href="https://web.archive.org/web/20111223225156/http://www.p25phase2.com:80/">"P25 Phase 2 Forum - Find an answer"</a>. Archived from <a href="http://www.p25phase2.com">the original</a> on 2011-12-23. Retrieved 2025-04-06.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">"What is P25 Technology?". Project 25 Technology Interest Group. Archived from the original on 29 April 2020. Retrieved 17 November 2020. Project 25 (P25) is the standard for the design and manufacture of interoperable digital two-way wireless communications products. Developed in North America with state, local and federal representatives and Telecommunications Industry Association (TIA) governance, P25 has gained worldwide acceptance for public safety, security, public service, and commercial applications...The P25 standard was created by, and is intended for, public safety professionals. <a href="https://www.project25.org/index.php/technology/what-is-p25-technology" target="_blank">https://www.project25.org/index.php/technology/what-is-p25-technology</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">"Project 25 Technology Interest Group - Content - General - What is Project 25?". project25.org. Project 25 Technology Interest Group. Archived from the original on 2009-02-10. Retrieved 2014-06-06. <a href="https://web.archive.org/web/20090210120900/http://www.project25.org/modules.php?name=Content&file=viewarticle&id=2" target="_blank">https://web.archive.org/web/20090210120900/http://www.project25.org/modules.php?name=Content&file=viewarticle&id=2</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">"What is P25?". Project25.org. Project 25 Technology Interest Group. Archived from the original on 2014-06-07. Retrieved 2014-06-06. <a href="https://web.archive.org/web/20140607000408/http://project25.org/component/content/article/29-content-articles/49-what-is-p25" target="_blank">https://web.archive.org/web/20140607000408/http://project25.org/component/content/article/29-content-articles/49-what-is-p25</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">"Project 25 Technology Interest Group - Content - General - What is Project 25?". project25.org. Project 25 Technology Interest Group. Archived from the original on 2009-02-10. Retrieved 2014-06-06. <a href="https://web.archive.org/web/20090210120900/http://www.project25.org/modules.php?name=Content&file=viewarticle&id=2" target="_blank">https://web.archive.org/web/20090210120900/http://www.project25.org/modules.php?name=Content&file=viewarticle&id=2</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">"Spectrum Management". Apcointl.org. 2013-09-30. Archived from the original on February 12, 2012. Retrieved 2014-06-06. <a href="https://web.archive.org/web/20120212013100/http://www.apcointl.org/frequency/project25/information.html" target="_blank">https://web.archive.org/web/20120212013100/http://www.apcointl.org/frequency/project25/information.html</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">"Home - National Association of State Technology Directors". www.nastd.org. <a href="http://www.nastd.org/home" target="_blank">http://www.nastd.org/home</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">"Spectrum Management". Apcointl.org. 2013-09-30. Archived from the original on February 12, 2012. Retrieved 2014-06-06. <a href="https://web.archive.org/web/20120212013100/http://www.apcointl.org/frequency/project25/information.html" target="_blank">https://web.archive.org/web/20120212013100/http://www.apcointl.org/frequency/project25/information.html</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">"SOR.book" (PDF). Retrieved 2010-09-26. <a href="http://www.safecomprogram.gov/NR/rdonlyres/3FFFBFBA-DC53-440E-B2EF-ABD391F13075/0/SAFECOM_Statement_of_Requirements_v1.pdf" target="_blank">http://www.safecomprogram.gov/NR/rdonlyres/3FFFBFBA-DC53-440E-B2EF-ABD391F13075/0/SAFECOM_Statement_of_Requirements_v1.pdf</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">"Why Can't We Talk?" (PDF). <a href="https://www.ncjrs.gov/pdffiles1/nij/204348.pdf" target="_blank">https://www.ncjrs.gov/pdffiles1/nij/204348.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">"A Google Company" (PDF). Motorola. Retrieved 2014-06-06. <a href="https://www.motorola.com/staticfiles/Business/Solutions/Business%20Solutions/Mission%20Critical%20Communications/ASTRO%2025%20Trunked%20Solutions/_Document/Project%2025%20Whitepaper.pdf?localeId=33" target="_blank">https://www.motorola.com/staticfiles/Business/Solutions/Business%20Solutions/Mission%20Critical%20Communications/ASTRO%2025%20Trunked%20Solutions/_Document/Project%2025%20Whitepaper.pdf?localeId=33</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">Search Results | IHS Standards Store <a href="http://global.ihs.com/search_res.cfm?currency_code=USD&customer_id=2125402A4E0A&oshid=2125402A4C0A&shopping_cart_id=292558332D4B20484B5B3D5B220A&country_code=US&lang_code=ENGL" target="_blank">http://global.ihs.com/search_res.cfm?currency_code=USD&customer_id=2125402A4E0A&oshid=2125402A4C0A&shopping_cart_id=292558332D4B20484B5B3D5B220A&country_code=US&lang_code=ENGL</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">Codan LTD., P25 Radio Systems Training Guide <a href="https://cdn.codancomms.com/general-downloads/Products/User-Guides/Codan_TG-001-4-0-0-P25-Training-Guide.pdf" target="_blank">https://cdn.codancomms.com/general-downloads/Products/User-Guides/Codan_TG-001-4-0-0-P25-Training-Guide.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">"p25expence". 31 May 2009. Retrieved 5 October 2016. <a href="http://forums.radioreference.com/general-scanning-discussion/146947-why-digital-scanners-so-expensive.html" target="_blank">http://forums.radioreference.com/general-scanning-discussion/146947-why-digital-scanners-so-expensive.html</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">"Aeroflex: Application Note - Understanding P25 Modulation Fidelity" (PDF). Archived from the original (PDF) on 2012-03-20. Retrieved 2012-03-26. <a href="https://web.archive.org/web/20120320083432/http://www.aeroflex.com/ats/products/prodfiles/appnotes/Understanding%20P25%20Modulation%20Fidelityiss1.pdf" target="_blank">https://web.archive.org/web/20120320083432/http://www.aeroflex.com/ats/products/prodfiles/appnotes/Understanding%20P25%20Modulation%20Fidelityiss1.pdf</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">"P25 Phase 2". Retrieved 9 December 2016. <a href="http://www.p25phase2.com/p25-phase-2" target="_blank">http://www.p25phase2.com/p25-phase-2</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">"P25 in Brazil". Retrieved 4 March 2020. <a href="https://www.teleco.com.br/tutoriais/tutorialprojeto25/default.asp" target="_blank">https://www.teleco.com.br/tutoriais/tutorialprojeto25/default.asp</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">"Mobile Broadband for Public Safety - Home Page". Project MESA. Archived from the original on 2008-10-20. Retrieved 2014-06-06. <a href="https://web.archive.org/web/20081020103132/http://www.projectmesa.org/" target="_blank">https://web.archive.org/web/20081020103132/http://www.projectmesa.org/</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">Advanced Mobile Broadband For Public Protection & Disaster Relief Professionals. David Thompson. Telecommunications Industry Association <a href="https://www.itu.int/dms_pub/itu-r/oth/0A/0E/R0A0E0000540001PDFE.pdf" target="_blank">https://www.itu.int/dms_pub/itu-r/oth/0A/0E/R0A0E0000540001PDFE.pdf</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Project MESA: Broadband Telecommunications for PPDR. David Thompson. Telecommunications Industry Association <a href="https://www.itu.int/itudoc/itu-t/workshop/ets/s5p1.pdf" target="_blank">https://www.itu.int/itudoc/itu-t/workshop/ets/s5p1.pdf</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">"www.projectmesa.org - /ftp/Specifications/". Archived from the original on June 13, 2010. <a href="https://web.archive.org/web/20100613000949/http://www.projectmesa.org/ftp/Specifications/" target="_blank">https://web.archive.org/web/20100613000949/http://www.projectmesa.org/ftp/Specifications/</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">"700 MHz Public Safety Spectrum". Federal Communications Commission. March 17, 2011. <a href="https://www.fcc.gov/700-mhz-public-safety-narrowband-spectrum" target="_blank">https://www.fcc.gov/700-mhz-public-safety-narrowband-spectrum</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">"P25 in Brazil - Tutorial by Dr. Cristiano Torres do Amaral from Brazilian Police Academy". Retrieved 4 March 2020. <a href="https://www.teleco.com.br/tutoriais/tutorialprojeto25/default.asp" target="_blank">https://www.teleco.com.br/tutoriais/tutorialprojeto25/default.asp</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">Is this finally P25's year?, Interview with Don Pfohl of Project 25 and Bill Belt of Telecommunications Industry Association's wireless division, 1. May 2005 <a href="http://urgentcomm.com/mag/radio_finally_ps_year/" target="_blank">http://urgentcomm.com/mag/radio_finally_ps_year/</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">Is this finally P25's year?, Interview with Don Pfohl of Project 25 and Bill Belt of Telecommunications Industry Association's wireless division, 1. May 2005 <a href="http://urgentcomm.com/mag/radio_finally_ps_year/" target="_blank">http://urgentcomm.com/mag/radio_finally_ps_year/</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">Is this finally P25's year?, Interview with Don Pfohl of Project 25 and Bill Belt of Telecommunications Industry Association's wireless division, 1. May 2005 <a href="http://urgentcomm.com/mag/radio_finally_ps_year/" target="_blank">http://urgentcomm.com/mag/radio_finally_ps_year/</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Is this finally P25's year?, Interview with Don Pfohl of Project 25 and Bill Belt of Telecommunications Industry Association's wireless division, 1. May 2005 <a href="http://urgentcomm.com/mag/radio_finally_ps_year/" target="_blank">http://urgentcomm.com/mag/radio_finally_ps_year/</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">Is this finally P25's year?, Interview with Don Pfohl of Project 25 and Bill Belt of Telecommunications Industry Association's wireless division, 1. May 2005 <a href="http://urgentcomm.com/mag/radio_finally_ps_year/" target="_blank">http://urgentcomm.com/mag/radio_finally_ps_year/</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">"Home - Motorola Solutions Australia & New Zealand". www.motorolasolutions.com. <a href="https://www.motorolasolutions.com/en_xa.html" target="_blank">https://www.motorolasolutions.com/en_xa.html</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">"Queensland Government Wireless Network". Archived from the original on 2017-02-18. <a href="https://web.archive.org/web/20170218183124/http://www.mingara.net.au/project/qld-gwn" target="_blank">https://web.archive.org/web/20170218183124/http://www.mingara.net.au/project/qld-gwn</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
<li id="fn:30">"Metropolitan Mobile Radio". www.esta.vic.gov.au. January 24, 2017. <a href="https://www.esta.vic.gov.au/mmr" target="_blank">https://www.esta.vic.gov.au/mmr</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></li>
<li id="fn:31">"Victoria Scanner Frequencies and Radio Frequency Reference". www.radioreference.com. <a href="https://www.radioreference.com/apps/db/?stid=152" target="_blank">https://www.radioreference.com/apps/db/?stid=152</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></li>
<li id="fn:32">"Public Safety Network". www.nsw.gov.au. 7 February 2022. <a href="https://www.nsw.gov.au/telco-authority/public-safety-network" target="_blank">https://www.nsw.gov.au/telco-authority/public-safety-network</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></li>
<li id="fn:33">"P25 CAP". Department of Homeland Security. 2016-05-22. Retrieved 2020-09-27. <a href="https://www.dhs.gov/science-and-technology/p25-cap" target="_blank">https://www.dhs.gov/science-and-technology/p25-cap</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></li>
<li id="fn:34">"P25 CAP". Department of Homeland Security. 2016-05-22. Retrieved 2020-09-27. <a href="https://www.dhs.gov/science-and-technology/p25-cap" target="_blank">https://www.dhs.gov/science-and-technology/p25-cap</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></li>
<li id="fn:35">"Approved Grant Eligible Equipment". Department of Homeland Security. February 6, 2017. <a href="https://www.dhs.gov/science-and-technology/approved-grant-eligible-equipment" target="_blank">https://www.dhs.gov/science-and-technology/approved-grant-eligible-equipment</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></li>
<li id="fn:36">"Approved Grant Eligible Equipment". Department of Homeland Security. 2017-02-06. Retrieved 2020-09-27. <a href="https://www.dhs.gov/science-and-technology/approved-grant-eligible-equipment" target="_blank">https://www.dhs.gov/science-and-technology/approved-grant-eligible-equipment</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></li>
<li id="fn:37">"P25 CAP Compliance: What Should It Mean to You?" (PDF). DHS Science and Technology Directorate. 2018. <a href="https://www.dhs.gov/sites/default/files/publications/900_P25-CAP_Construct_What-P25-CAP-Offers_180509_v2-508.pdf" target="_blank">https://www.dhs.gov/sites/default/files/publications/900_P25-CAP_Construct_What-P25-CAP-Offers_180509_v2-508.pdf</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></li>
<li id="fn:38">"SecureComm 2011 7th International ICST Conference on Security and Privacy in Communications Network". Archived from the original on 2012-02-03. Retrieved 2012-05-15. Securecomm 2011 <a href="https://web.archive.org/web/20120203173219/http://securecomm.org/2011/paperlist.shtml" target="_blank">https://web.archive.org/web/20120203173219/http://securecomm.org/2011/paperlist.shtml</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></li>
<li id="fn:39">"WikiStart - OP25 - Open Source Mobile Communications". osmocom.org. <a href="http://osmocom.org/projects/op25/wiki" target="_blank">http://osmocom.org/projects/op25/wiki</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></li>
<li id="fn:40">"GNU Radio - The Free & Open Source Radio Ecosystem · GNU Radio". GNU Radio. <a href="https://www.gnuradio.org/" target="_blank">https://www.gnuradio.org/</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></li>
<li id="fn:41">Brand, Ettus Research, a National Instruments. "Ettus Research - The leader in Software Defined Radio (SDR)". Ettus Research.{{cite web}}: CS1 maint: multiple names: authors list (link) <a href="https://www.ettus.com/" target="_blank">https://www.ettus.com/</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></li>
<li id="fn:42">"Insecurity in Public-Safety Communications: APCO Project 25". <a href="http://www.nicta.com.au/pub?doc=5076" target="_blank">http://www.nicta.com.au/pub?doc=5076</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></li>
<li id="fn:43">Valentino-DeVries, Jennifer (2011-08-10). "Security Flaws in Feds' Radios Make for Easy Eavesdropping". Wall Street Journal. Retrieved 2011-08-10. <a href="https://blogs.wsj.com/digits/2011/08/10/security-flaws-in-feds-radios-make-for-easy-eavesdropping/" target="_blank">https://blogs.wsj.com/digits/2011/08/10/security-flaws-in-feds-radios-make-for-easy-eavesdropping/</a> <a href="#fnref:43" class="footnote-back-ref">↩</a></li>
<li id="fn:44">"Why (Special Agent) Johnny (Still) Can't Encrypt: A Security Analysis of the APCO Project 25 Two-Way Radio system," S. Clark, T. Goodspeed, P. Metzger, Z. Wasserman, K. Xu, M. Blaze, Proceedings of the 20th Usenix Security Symposium, 2011 <a href="https://online.wsj.com/public/resources/documents/p25sec08102011.pdf" target="_blank">https://online.wsj.com/public/resources/documents/p25sec08102011.pdf</a> <a href="#fnref:44" class="footnote-back-ref">↩</a></li>
<li id="fn:45">"Why (Special Agent) Johnny (Still) Can't Encrypt: A Security Analysis of the APCO Project 25 Two-Way Radio system," S. Clark, T. Goodspeed, P. Metzger, Z. Wasserman, K. Xu, M. Blaze, Proceedings of the 20th Usenix Security Symposium, 2011 <a href="https://online.wsj.com/public/resources/documents/p25sec08102011.pdf" target="_blank">https://online.wsj.com/public/resources/documents/p25sec08102011.pdf</a> <a href="#fnref:45" class="footnote-back-ref">↩</a></li>
<li id="fn:46">"Design Issues for P25 Digital| National Interop". Archived from the original on 2011-07-14. Retrieved 2011-08-15. <a href="https://web.archive.org/web/20110714160000/http://www.nationalinterop.com/solutions_p25.html" target="_blank">https://web.archive.org/web/20110714160000/http://www.nationalinterop.com/solutions_p25.html</a> <a href="#fnref:46" class="footnote-back-ref">↩</a></li>
<li id="fn:47">P25 security mitigation guide, M. Blaze, et al. <a href="http://www.net-security.org/article.php?id=1617" target="_blank">http://www.net-security.org/article.php?id=1617</a> <a href="#fnref:47" class="footnote-back-ref">↩</a></li>
<li id="fn:48">"Pros and Cons of TETRA vs. P25 and the Benefits of a Multi-technology Platform for TETRA, P25 Phase I / Phase II, and Mobile WiMax" (PDF). Archived from the original (PDF) on 2012-09-04. <a href="https://web.archive.org/web/20120904073108/http://powertrunk.com/docs/Pros_and_Cons_of_P25_vs_TETRA.pdf" target="_blank">https://web.archive.org/web/20120904073108/http://powertrunk.com/docs/Pros_and_Cons_of_P25_vs_TETRA.pdf</a> <a href="#fnref:48" class="footnote-back-ref">↩</a></li>
<li id="fn:49">"P25 and TETRA Technology Roundtable". May 3, 2012. <a href="https://psc.apcointl.org/2012/05/03/p25-and-tetra-technology-roundtable/" target="_blank">https://psc.apcointl.org/2012/05/03/p25-and-tetra-technology-roundtable/</a> <a href="#fnref:49" class="footnote-back-ref">↩</a></li>
<li id="fn:50">https://tandcca.com/fm_file/dubai06swancomparison-pdf/ [dead link‍] <a href="https://tandcca.com/fm_file/dubai06swancomparison-pdf/" target="_blank">https://tandcca.com/fm_file/dubai06swancomparison-pdf/</a> <a href="#fnref:50" class="footnote-back-ref">↩</a></li>
</ol>

Project 25 open-in-new

Project 25