It has come to our attention that some local jurisdictions intending to purchase P25 CAP Compliant radios have instead been purchasing radios with a privacy voice non-standard algorithm, without the required AES-256 standard encryption, making those radios not P25 CAP compliant and, therefore, not eligible for Federal grant funding. Please be aware that compliance with P25 CAP requirements means radios must:
- Have no encryption;
- Have AES 256 (for U.S. agencies only); or
- Have AES 256 along with any other non-standard encryption algorithms.
If your jurisdiction has purchased a radio, after March 2017, that was intended to be P25 CAP Compliant or that was purchased with Federal grant funds and there is any doubt whether that radio meets one of the three conditions listed above, DHS encourages you to contact your manufacturer to confirm or take remedial action. For more information on this topic, please see the 2017 Encryption Requirements Compliance Assessment Bulletin and the posted letters on the subject supplied by the manufacturers.
Manufacturers should be cognizant that radios that do not meet DHS published Encryption Requirements are not P25 CAP compliant and may not be eligible for Federal grant funding.
The P25 stakeholder community had frequently raised the issue of manufacturers continually providing non-P25 standard encryption algorithms that ultimately would cause interoperability issues with neighboring agencies who were using P25 standard AES 256 encryption. The key concern was the potential impact non-standard encryption has on interoperability. To sum it up, when first responders from different jurisdictions use subscribers from different vendors but are not using the standards-based and P25 CAP approved AES 256 encryption, it is very possible successful and secure communications will not occur, thereby inhibiting interoperability. However, if a subscriber unit would provide the standards-based encryption (AES 256) at a minimum in addition to non-standards based encryption, users can then always use standards-based encryption during a mutual aid scenario or situations where users have different subscriber vendors/models and have a need to operate in an encrypted mode. P25 CAP sought to reach the point where the end user, who is seeking encryption, could be assured that the subscriber unit includes user access to that AES 256 encryption algorithm.
DHS S&T, with permission from each manufacturer, is making the correspondence received available. The manufacturers’ correspondence explains, in each manufacturer’s own words, the process each manufacturer is using to bring its equipment into compliance with the Encryption Requirements CAB and the process each manufacturer's customers would follow to ensure the equipment they are going to purchase or have already purchased would be or would be made P25 CAP Compliant.
CAP Test Documentation (STR and SDOCs)
The filters below can be used to search for P25 CAP Test documentation for equipment tested.