808bits

Johnson Encryption Machine 2 (JEM2)

FIPS 140-2 certificate #4080 · EF Johnson Technologies · data as of 2026-10-09

Johnson Encryption Machine 2 (JEM2), from EF Johnson Technologies, holds FIPS 140-2 certificate #4080 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode

Certificate

Certificate number4080
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorEF Johnson Technologies · website
Hardware versionsP/Ns R035-3900-180-00 and R035-3900-280-01
Firmware versions4.2

Module description

Quoted from the NIST CMVP entry for this certificate.

The EF Johnson Technologies Johnson Encryption Machine 2 (JEM2) is a cryptographic module meeting the FIPS140-2, Level 1 requirement. The JEM2 provides cryptographic operations to support Project 25 infrastructure. The JEM2 supports AES OTAR, AES Key Wrap, AES, ECDSA, DRBG, SHA-1, SHA-256, SHA-512, and HMAC FIPS Approved algorithms.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (7)

AlgorithmCAVP certificates
AES3436, 3437
CKGvendor affirmed
DRBG837
ECDSA692
HMAC2187
KTS
SHS2838

Allowed algorithms

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

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-11-30InitialUL 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2021-11-30

Source documents