808bits

Orbit MCR and Orbit ECR

FIPS 140-2 certificate #3634 · GE MDS LLC · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number3634
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorGE MDS LLC · website
Hardware versionsP/Ns MCR Chassis v1.0 and ECR Chassis v1.0; Component P/Ns: U91, L1B, L2X, L2B, L4A, L4E, L4C, L7A, L7W, L9C, 4G1, 4G2, 4G3, 4G4, 4G5, 4GP, 4GY, 4GZ, 4GA, E4S, E42, W51, W52, 3G1 and NNN (refer to Security Policy Tables 1 and 2 for valid combinations)
Firmware versions7.1.1 and 7.1.3

Module description

The GE MDS Orbit Multiservice Connect Router (MCR) and Edge Connect Router (ECR) modules are secure wireless communications devices, which operate on cellular bands (2G/3G/4G LTE), licensed and unlicensed bands, and 802.11 Wi-Fi. The modules are available in two form factors (MCR and ECR), with different port/interface configurations available for each.

Approved algorithms

AlgorithmCAVP certificate
AES4539, 5887, 5888, 5889
CKGvendor affirmed
CVL1219, 1221, 2118
DRBG1496, 2450
DSA1210, 1484
HMAC2997, 3864
KDAvendor affirmed
KTS
KTS
KTS
PBKDFvendor affirmed
RSA2471, 3085
SHS3720, 4639, 4640
Triple-DES2416, 2867, 2868

Allowed algorithms

Diffie-Hellman (CVL Cert. #1219, key agreement; key establishment methodology provides 112 or 128 bits of encryption strength); Diffie-Hellman (CVL Cert. #1221, key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; NDRNG; RSA (key agreement; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2020-03-20InitialUL Verification Services, Inc.
2021-07-05UpdateUL 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: 2020-03-20, 2021-07-05

Source documents