808bits

Vormetric Data Security Manager Virtual Appliance Module

FIPS 140-2 certificate #2735 · Vormetric, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The protocol SSH shall not be used when operated in FIPS mode

Certificate

Certificate number2735
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorVormetric, Inc. · website
Software versions5.3.0

Module description

The Vormetric Data Security Virtual Appliance Module is a multi-chip standalone cryptographic module. The Vormetric Data Security Virtual Appliance Module is the central point of management for the Vormetric Data Security product. It manages keys and policies, and controls Vormetric Transparent Encryption Agents. These agents contain the Vormetric Encryption Expert Cryptographic Module, which has been validated separately from this module.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Physical Security: N/A
  • Cryptographic Key Management: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3588, 3621
CVL612, 643
DRBG951
ECDSA751
HMAC2287, 2288, 2375
KTS
RSA1866
SHS2949, 2950, 3041

Other algorithms

EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); Aria; SSH KDF (non-compliant); Triple-DES (non-compliant)

Tested configurations

  • Centos 5.11 (64-bit) on VMware ESXi 5.5.0 running on a Supermicro X9DAX (single-user mode)

Validation history

DateTypeLab
2016-09-02InitialCYGNACOM SOLUTIONS 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-09-02

Source documents