808bits

Nexus FIPS 140-2 Crypto Module

FIPS 140-2 certificate #1238 · Nexus Wireless · data as of 2026-10-09

Nexus FIPS 140-2 Crypto Module, from Nexus Wireless, holds FIPS 140-2 certificate #1238 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1238
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip embedded
VendorNexus Wireless · website
Hardware versions1.0
Firmware versionsES0408_RL01_R1_00_000 version 1.00.000 and ES0408_RL02_R1_00_000 version 1.00.000

Module description

Quoted from the NIST CMVP entry for this certificate.

The Nexus FIPS140-2 Crypto Module is a single-board security module designed to conform to FIPS140-2 standards and primarily intended for use in P25 radio equipment. The module supports both KFD and KMF management implementations, including a dedicated 3-wire KFD interface. It includes a complete key storage and critical security material management function for TEK, KEK, UKEK, CKEK and KSKEK keys in non-volatile memory within the FIPS module, with protection from unauthorized disclosure or modification. The FIPS Module executes encryption and decryption of P25 Phase 1 voice and data.

Approved algorithms (5)

AlgorithmCAVP certificates
AES914
DSA337
HMAC533
RNG524
SHS901, 928

Other algorithms

DES; AES MAC (AES Cert. #914, vendor affirmed; P25 AES OTAR)

Validation history

DateTypeLab
2010-01-05InitialCOACT INC CAFE LAB

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2010-01-05

Source documents