808bits

CoreGuard Security Server

FIPS 140-2 certificate #442 · 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

Certificate

Certificate number442
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorVormetric, Inc. · website
Hardware versionsP/N 30 Release 1.0 Version 3.0
Firmware versionsVN.3.0SP1- Build0060 and VN.3.0SP1-Build0064

Module description

Vormetric CoreGuard Security Server is a comprehensive security solution that combines protection of data at rest, application integrity and host protection. CoreGuard integrates a software module loaded on a server, and a FIPS compliant appliance with user-defined security policies allowing fine-grain data access control and selective encryption of data at rest (AES 128/256 and 3DES), application digital signatures, enforced user authentication, host protection and central management. CoreGuard installs transparently and does not require changes to applications, databases or storage architectures allowing the security to extend to any data across the enterprise.

Security level exceptions

  • Cryptographic Module Ports and Interfaces: Level 3
  • Roles, Services, and Authentication: Level 3
  • Cryptographic Key Management: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES135
HMAC-SHA-1vendor affirmed
RSAvendor affirmed
SHA-1218
Triple-DES241

Other algorithms

Diffie-Hellman (key agreement); MD5

Validation history

DateTypeLab
2004-06-16InitialUL Verification Services, Inc.
2004-07-27Update
2006-01-27Update

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: 2004-06-16, 2004-07-27, 2006-01-27

Source documents