808bits

HyTrust KeyControl (TM) Cryptographic Module

FIPS 140-2 certificate #2524 · HyTrust, Inc. · data as of 2026-10-09

HyTrust KeyControl (TM) Cryptographic Module, from HyTrust, Inc., holds FIPS 140-2 certificate #2524 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2524
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorHyTrust, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

HyTrust KeyControl is a key management system that is available in three different formats (ISO, OVA and AMI) and can be run on physical x86 based hardware as a virtual machine and on one of a number of different hypervisor platforms or as a combination of both when running in clustered mode.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (4)

AlgorithmCAVP certificates
AES3397, 3431, 3432
DRBG813
HMAC2168
SHS2813

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); NDRNG

Tested configurations

  • FreeBSD 9.2 on VMware vSphere Hypervisor (ESXi) 5.5.0u2 on Dell Inc. PowerEdge R220, Intel Xeon CPU E3-1241v3 @ 3.50GHz (single user mode)

Validation history

DateTypeLab
2016-01-05InitialAEGISOLVE, Inc.

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: 2016-01-05

Source documents