808bits

Subscriber Encryption Module

FIPS 140-2 certificate #2245 · EF Johnson Technologies · data as of 2026-09-03

Subscriber Encryption Module, from EF Johnson Technologies, holds FIPS 140-2 certificate #2245 at overall level 1. 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. 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

Certificate

Certificate number2245
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip embedded
VendorEF Johnson Technologies · website
Hardware versionsR023-5000-980
Firmware versions5.28

Module description

Quoted from the NIST CMVP entry for this certificate.

The EFJohnson Subscriber Encryption Module (SEM) is a cryptographic module meeting FIPS 140-2, Level 1 requirements. The SEM provides Subscriber Equipment, such as the EFJohnson Technology VP600 series radio with secure encrypted voice communication. The SEM supports AES, RSA, HMAC, DRBG and SHA-256 FIPS Approved algorithms for voice communication and protection of its firmware. The SEM can be implemented into any Subscriber Equipment requiring FIPS 140-2, Level 1 security.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (6)

AlgorithmCAVP certificates
AES2640
DRBG411
HMAC1632
KTS
RSA1351
SHS2213

Other algorithms

AES MAC (AES Cert. #2640, vendor affirmed; P25 AES OTAR); NDRNG

Validation history

DateTypeLab
2014-09-10InitialUL Verification Services, Inc.
2018-04-24UpdateUL Verification Services, Inc.
2019-04-30UpdateUL 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: 2014-09-10, 2018-04-24, 2019-04-30

Source documents