808bits

Vormetric Data Security Manager Virtual Appliance Module

FIPS 140-2 certificate #3443 · Thales eSecurity · 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. The protocol SSH shall not be used when operated in FIPS mode.

Certificate

Certificate number3443
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorThales eSecurity · website
Software versions6.0.2

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
AES4846, 5536
CKGvendor affirmed
CVL1482, 1979
DRBG1703
ECDSA1240
HMAC3246, 3688
KTS
KTS
RSA2664, 2970
SHS3987, 4443

Allowed algorithms

EC Diffie-Hellman (CVL Certs. #1482 and #1979, key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • Centos 7.2 (64 bits) on VMware ESXi 6.5 running on a Supermicro SSG-2028R-E1CR24N with an Intel Xeon (single-user mode)

Validation history

DateTypeLab
2019-04-26InitialCYGNACOM 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: 2019-04-26

Source documents