808bits

Tropos Wireless IP Mesh Router

FIPS 140-2 certificate #1245 · Tropos Networks · data as of 2026-09-08

Tropos Wireless IP Mesh Router, from Tropos Networks, holds FIPS 140-2 certificate #1245 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. 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 and with the tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number1245
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorTropos Networks · website
Hardware versions5320-2531, 5320-2631, 5320-3030, 5320-3130, 5320-6000, 5320-6060, 6310-3030, 6320-2531, 6320-3030, 7320-2531, 7320-2631, 7320-3030, 7320-3130, 7320-6000 and 7320-6060
Firmware versions7.3

Module description

Quoted from the NIST CMVP entry for this certificate.

Tropos's single/multi-radio, wireless 802.11 a/b/g/n Wireless IP Mesh routers provide a secure, high-performance, easy to deploy, and cost-effective networking solution for outdoor environments. Tropos routers support IEEE 802.1X and 802.11i with AES encryption and secure EAP types while operating in FIPS 140-2 mode.

Approved algorithms (6)

AlgorithmCAVP certificates
AES993, 1082, 1083, 1085
HMAC559, 607
RNG562
RSA477
SHS959, 1017
Triple-DES774

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); Blowcrypt; MD5; RC4

Validation history

DateTypeLab
2010-01-15InitialSAIC-VA

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-15

Source documents