808bits

Hydra PC FIPS Sector-based Encryption Module

FIPS 140-2 certificate #1215 · SPYRUS, Inc. · data as of 2026-10-21

Hydra PC FIPS Sector-based Encryption Module, from SPYRUS, Inc., holds FIPS 140-2 certificate #1215 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1215
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorSPYRUS, Inc. · website
Hardware versionsP/N 88007021F, Version 01.00.02
Firmware versions03.00.04

Module description

Quoted from the NIST CMVP entry for this certificate.

The Hydra PC FIPS Sector-based Encryption Module provides hardware-based, sector by sector full disk encryption providing the protective military strength of the U. S. Government's Suite B algorithm standards, including AES, ECDSA, SHA-2, and EC-DH. The USB encryption device comes with an easy to use, user-friendly interface that operates on the Microsoft Windows operating systems without installing any drivers.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Roles, Services, and Authentication: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms (6)

AlgorithmCAVP certificates
AES1015, 1016
DRBG10
ECDSA122
KASvendor affirmed
RNG582
SHS972, 973, 974

Other algorithms

EC-Diffie-Hellman (key agreement; key establishment methodology provides 128, 192 or 256 bits of encryption strength)

Validation history

DateTypeLab
2009-10-22InitialUL Verification Services, Inc.
2010-05-05Update

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: 2009-10-22, 2010-05-05

Source documents