808bits

VMware VMkernel Cryptographic Module

FIPS 140-2 certificate #3073 · VMware, Inc. · data as of 2026-10-21

VMware VMkernel Cryptographic Module, from VMware, Inc., holds FIPS 140-2 certificate #3073 at overall level 1. 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.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number3073
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorVMware, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The VMware VMkernel Cryptographic Module is a software cryptographic library that provides FIPS 140-2 Approved cryptographic services for VMware products and platforms.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (5)

AlgorithmCAVP certificates
AES4531, C1172
AES-CBC-CSvendor affirmed
DRBG1488, C1172
HMAC2989, 3048, C1171, C1172
SHS3712, 3774, C1171, C1172

Allowed algorithms

NDRNG

Tested configurations

  • VMware ESXi 6.7 on a Dell PowerEdge R740 with Intel Xeon Gold 6126 with PAA
  • VMware ESXi 6.7 on a Dell PowerEdge R740 with Intel Xeon Gold 6126 without PAA
  • VMWare ESXi 6.7 on a Dell PowerEdge R830 with Intel Xeon E5 with PAA
  • VMWare ESXi 6.7 on a Dell PowerEdge R830 with Intel Xeon E5 without PAA
  • VMware ESXi 7.0 on a Dell PowerEdge R740 with Intel Xeon Gold 6126 with PAA
  • VMware ESXi 7.0 on a Dell PowerEdge R740 with Intel Xeon Gold 6126 without PAA (single-user mode)

Validation history

DateTypeLab
2017-12-05InitialAcumen Security
2020-06-19UpdateAcumen Security

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-12-05, 2020-06-19

Source documents