808bits

V2VNet Common Crypto Module

FIPS 140-2 certificate #2081 · Dispersive Technologies, Inc. · data as of 2026-09-08

V2VNet Common Crypto Module, from Dispersive Technologies, Inc., holds FIPS 140-2 certificate #2081 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: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2081
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorDispersive Technologies, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

V2VNet Common Crypto Module provides cryptographic functions for Dispersive Solutions V2VNet Server Edition, a scalable solution allowing clients to communicate directly with other clients, and securely route voice, video and data communications.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES2273
CKGvendor affirmed
DRBG281
DSA709
ECDSA368
HMAC1391
RSA1166
SHS1954
Triple-DES1420

Tested configurations

  • CentOS 6.3 on a Dell OptiPlex 755
  • Mac OS X 10.8 on a MacBook Air (single-user mode)
  • Windows Server 2008 R2 on a Dell OptiPlex 755

Validation history

DateTypeLab
2014-02-22InitialEWA - Canada
2015-09-18UpdateEWA - Canada
2016-02-26UpdateAcumen Security
2022-01-18UpdateAEGISOLVE, Inc.

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: 2014-02-22, 2015-09-18, 2016-02-26, 2022-01-18

Source documents