808bits

BlackVault HSM

FIPS 140-2 certificate #3029 · Engage Communication, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number3029
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorEngage Communication, Inc. · website
Hardware versions007-BVES-01
Firmware versions7.0.10.2

Module description

The BlackVault HSM is a portable or embeddable Ethernet attached Hardware Security Module that combines a cryptographically advanced HSM with a Smart Card Reader and integrated touch screen display. The BlackVault HSM is a standards based security module that performs key management and cryptographic operations for: application data, regulatory compliance and critical security systems employed by governments, PKI, and enterprises. Two-factor authentication and administrator roles with M of N prevents unauthorized access to critical security parameters.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES2767, 2768, 2801, 4038
CVL295, 864, 865, 1200
DRBG468
DSA1093
ECDSA904
HMAC1732
KTS
RSA2073, 2366
SHS2327, 3606, 3607

Allowed algorithms

EC Diffie-Hellman (CVL Cert. #295, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-09-27InitialUL Verification Services, Inc.
2018-03-08UpdateUL Verification Services, Inc.
2018-07-03UpdateUL Verification Services, 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: 2017-09-27, 2018-03-08, 2018-07-03

Source documents