808bits

Chrysalis-ITS K3 Cryptographic Engine

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

Chrysalis-ITS K3 Cryptographic Engine, from SafeNet, Inc., holds FIPS 140-2 certificate #375 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. 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 number375
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorSafeNet, Inc. · website
Hardware versions2.0, 3.0 and 4.0
Firmware versions4.1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The K3 Chrysalis-ITS Cryptgraphic Engine is a hardware cryptographic module in the form of a PCI card that resides within a secured generalpurpose computing appliance. It is contained in its own secure enclosure that provides physical resistance to tampering and zeroization in the event the enclosure is opened. The cryptographic boundary of the module is defined to encompass all components inside the secure enclosure on the PCI card.

Approved algorithms (7)

AlgorithmCAVP certificates
AES41
DSA51
HMAC-SHA-1vendor affirmed
RSAvendor affirmed
SHA- 1
Triple-DES73
Triple-DES MACvendor affirmed

Other algorithms

DES (Cert. #32); DES MAC (Cert. #32, vendor affirmed); RC2; RC4; RC5; CAST; CAST3; CAST5; MD2; MD5; Diffie-Hellman 1024; CAST MAC; CAST3 MAC; CAST5 MAC; SEED; SSL3-MD5 MAC; SSL3-SHA-1 MAC; HMAC-MD5; KCDSA; PBE-MD2-DES; PBE-MD5-DES; PBE-MD5-CAST; PBE-MD5-CAST3; PBE-SHA-1-CAST5; AES MAC; RC2 MAC; RC5-MAC

Validation history

DateTypeLab
2004-01-30InitialDOMUS
2004-10-18Update
2005-12-22Update

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: 2004-01-30, 2004-10-18, 2005-12-22

Source documents