808bits

SLM-5650A TRANSEC Module

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

SLM-5650A TRANSEC Module, from Comtech EF Data Corporation, holds FIPS 140-2 certificate #1553 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

Certificate

Certificate number1553
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip embedded
VendorComtech EF Data Corporation · website
Hardware versions1.2
Firmware versions1.2.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The SLM-5650 satellite modem includes a single FIPS card called the SLM-5650A TRANSEC Module that will perform bulk encryption of all packets for transmission over the satellite regardless of the protocol, the format of data, or existing encryption on the incoming data. The SLM-5650A TRANSEC Module uses 256-bit AES in CBC mode for bulk encryption of all data requiring encryption. The module is managed using a proprietary graphical user interface (GUI) over TLS, referred to as the Management & Control Console, and a command line management interface over SSH.

Approved algorithms (7)

AlgorithmCAVP certificates
AES1537, 1538
ECDSA189
HMAC893
RNG827
RSA746
SHS1363
Triple-DES1012

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Validation history

DateTypeLab
2011-06-07InitialSAIC-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: 2011-06-07

Source documents