808bits

jForté/HAT Cryptographic Module

FIPS 140-2 certificate #611 · Litronic, Inc. · data as of 2026-09-12

jForté/HAT Cryptographic Module, from Litronic, Inc., holds FIPS 140-2 certificate #611 at overall level 3. 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: None

Certificate

Certificate number611
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorLitronic, Inc. · website
Hardware versionsP/N 078-2010-02 Version J002
Firmware versions3.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The high assurance jForté/HAT module is a multi-function, secure device, specifically engineered to provide expanded storage and accelerated processing of complex cryptographic functions. jForté/HAT also provides high data throughput via its dual I/O interface, supporting both ISO7816-3 and Full Speed USB. The module is available in several different packaging configurations - smart card module, 24-pin SOIC or bare die. Our patented smart card packaging provides access to both 7816-3 and USB interfaces so the same smart card will work in both standard readers, at 7816 speeds, and in high-speed USB readers and Full Speed USB.

Security level exceptions

  • Physical Security: Level 4

Approved algorithms (6)

AlgorithmCAVP certificates
RNG59
RSA46
SHS294
Skipjack15
Triple-DES306
Triple-DES MACvendor affirmed

Other algorithms

DES (Cert. #289); DES MAC (Cert. #289, vendor affirmed)

Validation history

DateTypeLab
2005-12-23InitialUL 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: 2005-12-23

Source documents