808bits

Proteus MX Licensed Band Radio Cryptographic Module

FIPS 140-2 certificate #2816 · Microwave Networks Inc. · data as of 2026-10-09

Proteus MX Licensed Band Radio Cryptographic Module, from Microwave Networks Inc., holds FIPS 140-2 certificate #2816 at overall level 2. 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with the tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number2816
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorMicrowave Networks Inc. · website
Hardware versionsP/Ns 8209361-10 Rev A03 [1], 8209361-12 Rev A03 [1], 8209361-14 Rev A03 [1], 8209363-10 Rev A03 [2], 8209363-12 Rev A03 [2] and 8209363-14 Rev A03 [2]
Firmware versions8746006-02 Rev A02 [1] or 8746007-02 Rev A02 [2]

Module description

Quoted from the NIST CMVP entry for this certificate.

The module is a cryptographic device enclosed in a plug-in chassis that provides mux/demux and mod/dmod functions along with optional payload encryption for a line of license band point-to-point radios.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (5)

AlgorithmCAVP certificates
AES4080, 4082
CVL900
DSA1107
HMAC2664
SHS3360

Other algorithms

HMAC-SHA-1-96 (HMAC Cert. #2664); DES; Diffie-Hellman; HMAC (non-compliant); HMAC-MD5; MD5; PRNG; RC4; SHS (non-compliant); Triple-DES (non-compliant)

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-01-12InitialUL Verification Services, Inc.

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: 2017-01-12

Source documents