808bits

Luna® XLR

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

Luna® XLR, from SafeNet, Inc., holds FIPS 140-1 certificate #217 at overall level 2. 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. Validation Sunsetting Policy - FIPS 140-1 Certificate. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number217
StandardFIPS 140-1
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Hardware versionsLXL-002-101 and LXL-003-001
Firmware versions3.96

Module description

Quoted from the NIST CMVP entry for this certificate.

Luna® XLR provides high-performance hardware-based key management and cryptographic acceleration for secure web servers, e-commerce servers and Internet-based financial systems in a 1U Rack-mount form factor. Luna® XLR offers a highly secure solution for SSL transaction processing, based on the key management strength of the Luna® cryptographic engine and, at the same time, offers easily scalable improvement in system performance.

Security level exceptions

  • Physical Security: Level 3
  • EMI/EMC: Level 3
  • Software Security: Level 3
  • Self Tests: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
DSA51
SHA-164
Triple-DES73
Triple-DES MAC; RSAvendor affirmed

Other algorithms

DES (Cert. #134); DES MAC; RC2; RC4; RC5; CAST; CAST3; CAST5; CAST MAC; CAST 3 MAC; CAST 5 MAC; MD2; MD5; Diffie-Hellman (key agreement); RSA (Encryption/Decryption);

Validation history

DateTypeLab
2002-04-30InitialDOMUS
2004-10-18Update

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: 2002-04-30, 2004-10-18

Source documents