CoreGuard Security Server
CoreGuard Security Server, from Vormetric, Inc., holds FIPS 140-2 certificate #442 at overall level 2. 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.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 442 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Vormetric, Inc. · website |
| Hardware versions | P/N 30 Release 1.0 Version 3.0 |
| Firmware versions | VN.3.0SP1- Build0060 and VN.3.0SP1-Build0064 |
Module description
Quoted from the NIST CMVP entry for this certificate.
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 (5)
Other algorithms
Diffie-Hellman (key agreement); MD5
Validation history
| Date | Type | Lab |
|---|---|---|
| 2004-06-16 | Initial | UL Verification Services, Inc. |
| 2004-07-27 | Update | |
| 2006-01-27 | Update |
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