808bits

Unified Crypto Module

FIPS 140-2 certificate #3011 · Comtech EF Data Corporation · data as of 2026-09-15

Unified Crypto Module, from Comtech EF Data Corporation, holds FIPS 140-2 certificate #3011 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. 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 number3011
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorComtech EF Data Corporation · website
Hardware versionsPL-0000235-2
Firmware versions2.2.4

Module description

Quoted from the NIST CMVP entry for this certificate.

The Comtech Unified Crypto Module features an FPGA to perform bulk encryption/decryption for Ethernet data traffic via Comtech Satellite Modems, as well as firmware to provide the cryptographic functions needed to act as a endpoint for secure TLS- and SSH-based management and control traffic.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (10)

AlgorithmCAVP certificates
AES4077, 4078, 4079
CKGvendor affirmed
CVL899, 1084
DRBG1225
ECDSA922
HMAC2663
KBKDF131
RSA2209
SHS3359
Triple-DES2229

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #899, key agreement; key establishment methodology provides 256 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
2017-09-07InitialCGI Information Systems & Management Consultants 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-09-07

Source documents