808bits

Enhanced Bandwidth Efficient Modem (EBEM) Cryptographic Module

FIPS 140-2 certificate #3351 · Viasat, Inc. · 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: The tamper evident seal installed as indicated in the security policy for the optional ESEM feature

Certificate

Certificate number3351
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorViasat, Inc. · website
Hardware versionsP/Ns 1010162 Version 1, 1010162 with ESEM Version 1, 1091549 Version 1, 1075559 Version 1, 1075559 with ESEM Version 1, 1091551 Version 1, 1010163 Version 1, 1010163 with ESEM Version 1, 1091550 Version 1, 1075560 Version 1, 1075560 with ESEM Version 1 and 1091552 Version 1; P/N 1047117 (tamper evident seal applied over ESEM)
Firmware versions02.11.06

Module description

The Enhanced Bandwidth Efficient Modem (EBEM), MD-1366/U is a high-performance multi-input multi-output single channel per carrier (SCPC) satellite modem that converts multiple baseband digital input signals into multiple waveform intermediate frequencies (IF) and vice­versa. The EBEM is intended for use with Government and commercial satellite systems.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3449, 3450, 5475, 5476
CKGvendor affirmed
CVL1928, 1929, 1930
DRBG2154
ECDSA1466, 1467
HMAC3630, 3631
KAS182
KTS
SHS2689, 4393, 4394

Allowed algorithms

EC Diffie-Hellman (CVL Certs. #1928 and #1929, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-01-28InitialUL 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: 2019-01-28

Source documents