808bits

PCoIP Cryptographic Module for VMware View

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

PCoIP Cryptographic Module for VMware View, from VMware, Inc., holds FIPS 140-2 certificate #1644 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.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1644
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeSoftware
EmbodimentMulti-chip standalone
VendorVMware, Inc. · website
Software versions3.5.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The PCoIP Cryptographic module for VMware View is a multi-chip standalone cryptographic module evaluated for use on a standard General Purpose Computer (GPC) platform. The overal security level is Level 2. The module consists of a single shared library which is used by both the PCoIP server and the PCoIP client applications.

Security level exceptions

  • Roles, Services, and Authentication: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES1639, 1640, 1642
HMAC964
RNG879
SHS1443

Other algorithms

Salsa12; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Microsoft Windows XP running on a Dell Optiplex GX260
  • Microsoft Windows XP running on a Dell Poweredge 2850
  • Red Hat Enterprise Linux (RHEL) 5.1 running on a Dell Poweredge 2850

Validation history

DateTypeLab
2011-12-06InitialEWA - Canada

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: 2011-12-06

Source documents