808bits

Scalar Key Manager

FIPS 140-2 certificate #1445 · Quantum Corporation · data as of 2026-09-08

Scalar Key Manager, from Quantum Corporation, holds FIPS 140-2 certificate #1445 at overall level 1. 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 with the Red Hat Enterprise Linux 5 OpenSSL Cryptographic Module validated to FIPS 140-2 under Cert. #1320 operating in FIPS mode (approved algorithms retested on listed operating environment)

Certificate

Certificate number1445
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorQuantum Corporation · website
Software versions2.0.3.a

Module description

Quoted from the NIST CMVP entry for this certificate.

The Scalar Key Manager implements a client/server interface for key administration. The user application has the client role, and the key manager has the server role. The user opens a secure connection to the key server, sends an administrative request (create a key, change a key, etc.), receives a response from the server, and the session is disconnected.

Approved algorithms (5)

AlgorithmCAVP certificates
AES1255, 1499
HMAC734, 882
RNG698, 816
RSA736
SHS1151, 1350

Other algorithms

MD5, RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • rPath Linux, Version 2.6.29 (single-user mode)

Validation history

DateTypeLab
2010-11-15Initialatsec information security corporation
2010-12-06Update
2011-03-15Updateatsec information security corporation

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: 2010-11-15, 2010-12-06, 2011-03-15

Source documents