808bits

VMware's VPN Crypto Module

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

VMware's VPN Crypto Module, from VMware, Inc., holds FIPS 140-2 certificate #4286 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode

Certificate

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

Module description

Quoted from the NIST CMVP entry for this certificate.

VMware's VPN Crypto Module is a software cryptographic module whose purpose is to provide FIPS 140-2 validated cryptographic functions to various VMware applications utilizing VPN capabilities.

Security level exceptions

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

Approved algorithms (4)

AlgorithmCAVP certificates
AESA1917
HMACA1917, A1918
SHSA1917, A1918
Triple-DESA1917

Tested configurations

  • Ubuntu 18.04 on ESXi 7.0 running on a Dell PowerEdge R740 with Intel Xeon Gold 6230R with PAA
  • Ubuntu 18.04 on ESXi 7.0 running on a Dell PowerEdge R740 with Intel Xeon Gold 6230R without PAA (single-user mode)

Validation history

DateTypeLab
2022-08-30InitialAcumen Security
2024-11-07UpdateAcumen 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-08-30, 2024-11-07

Source documents