808bits

MPU5

FIPS 140-2 certificate #3234 · Persistent Systems, LLC · data as of 2026-08-28
Historical. SP 800-56Arev3 transition - replaced by certificate #4514. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When initialized and configured to overall level 2 per the Security Policy. The tamper evident material installed as indicated in the Security Policy

Certificate

Certificate number3234
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorPersistent Systems, LLC · website
Hardware versionsP/N WR-5100, Versions: 4.0.B, 4.1.B, 4.2.B, 4.2.C, 4.3.A, 4.3.B, 4.3.C, 4.3.D, 4.4.B, 4.4.C, 4.4.D, 4.5.C, 4.5.D, 4.6.D, 4.6.K, 4.6L and 4.6M; Tamper Evident Paint P/N PROD-007
Firmware versions19.5.5 and 19.6.4

Module description

The MPU5 and Wave Relay® MANET provide wireless network connectivity between highly mobile users in a true peer-to-peer topology without requiring additional infastructure. The MPU5 is designed to be carried by dismount users or mounted on towers, vehicles and aircraft.

Security level exceptions

  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4455, 4456
CKGvendor affirmed
CVL1161, 1162, 1163
DRBG1443
ECDSA1085
HMAC2955, 2956, 2957
KTS
RSA2433
SHS3666, 3667, 3668

Allowed algorithms

EC Diffie-Hellman (CVL Cert. #1161, key agreement; key establishment methodology provides 192 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-07-17InitialUL Verification Services, Inc.
2018-12-12UpdateUL Verification Services, Inc.
2019-04-08UpdateUL Verification Services, Inc.
2020-11-24UpdateUL Verification Services, Inc.
2021-08-30UpdateUL 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: 2018-07-17, 2018-12-12, 2019-04-08, 2020-11-24, 2021-08-30

Source documents