808bits

DSI V2VNet Mobile Crypto Module

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

DSI V2VNet Mobile Crypto Module, from Dispersive Technologies, Inc., holds FIPS 140-2 certificate #2013 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 makes no assurance of the minimum strength of random strings and generated keys. This validation entry is a non-security relevant modification to Cert. #1938.

Certificate

Certificate number2013
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 Mobile Crypto Module provides cryptographic functions for Dispersive Solutions V2VNet Mobile Edition, a scalable solution allowing clients to communicate directly with other clients, and securely route voice, video and data communications.

Security level exceptions

  • Design Assurance: Level 3

Approved algorithms (9)

AlgorithmCAVP certificates
AES2125, 2126
CKGvendor affirmed
DRBG233, 234
DSA666, 667
ECDSA319, 320
HMAC1296, 1297
RSA1094, 1095
SHS1845, 1850
Triple-DES1351, 1352

Tested configurations

  • Android 4.0 running on a Galaxy Nexus
  • iOS 5.1 running on a iPad 3
  • iOS 6 running on a iPad 3
  • iOS 7 running on a iPad 3 (single-user mode)

Validation history

DateTypeLab
2013-11-05InitialEWA - Canada
2015-09-18UpdateEWA - Canada
2022-02-25UpdateAEGISOLVE, 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: 2013-11-05, 2015-09-18, 2022-02-25

Source documents