808bits

Rajant BreadCrumb ME4-2409

FIPS 140-2 certificate #2740 · Rajant Corporation · data as of 2026-08-28
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 and with the tamper evident seals installed as indicated in the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2740
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorRajant Corporation · website
Hardware versionsME4-2409 with FIPS Kit: P/N 42540
Firmware versions11.4.0-FIPS

Module description

The BreadCrumb by Rajant Corporation is an 802.11 (Wi-Fi) and Ethernet compatible wireless mesh networking device that allows for rapid deployment of mobile wireless networks in a wide variety of environments. It is lightweight, capable of communicating via up to four different radio frequencies, and is designed to be completely mobile as carried by a vehicle or an individual. BreadCrumb devices automatically detect other BreadCrumb devices and dynamically route packets through the resulting wireless mesh on behalf of commercially available off-the-shelf client devices.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3445
CVL531, 539
DRBG842
HMAC2194
KBKDF64
RSA1765
SHS2845

Other algorithms

AES (non-compliant); Camellia-CBC; NDRNG; PBKDF (non-compliant); RC4; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); Triple-DES (non-compliant)

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-09-08InitialCOACT 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: 2016-09-08

Source documents