808bits

Luna® PCI Cryptographic Module for Luna® IS and RSS

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

Luna® PCI Cryptographic Module for Luna® IS and RSS, from SafeNet, Inc., holds FIPS 140-2 certificate #1656 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: When operated in FIPS mode

Certificate

Certificate number1656
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorSafeNet, Inc. · website
Hardware versionsVBD-03-0100
Firmware versions5.2.7 and 5.2.8

Module description

Quoted from the NIST CMVP entry for this certificate.

The Luna® PCI for Luna® IS offers hardware-based key management and cryptographic operations to protect sensitive keys. The cryptographic boundary of the module is defined to encompass all components inside the secure enclosure on the PCI card.

Approved algorithms (9)

AlgorithmCAVP certificates
AES510, 1737, 1738
DSA542, 543
ECDSA228, 229
HMAC1014, 1015
RNG925, 926
RSA860, 861
SHS1522, 1523
Triple-DES520, 1126, 1127
Triple-DES MACvendor affirmed

Other algorithms

AES MAC (Certs. #510, #910 and #913; non-compliant); CAST5; CAST5-MAC; DES; Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); HAS-160; HAS-160 MAC; KCDSA; MD2; MD5; RC2; RC4; RC5; SEED; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2011-12-22InitialSAIC-VA
2012-01-11UpdateSAIC-VA

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: 2011-12-22, 2012-01-11

Source documents