808bits

VME Crypto Engine

FIPS 140-2 certificate #505 · Meganet Corporation · data as of 2026-10-09

VME Crypto Engine, from Meganet Corporation, holds FIPS 140-2 certificate #505 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 with the Microsoft® Base Cryptographic Provider validated to FIPS 140-1 under Certificate #238 operating in FIPS mode for the operating systems specified

Certificate

Certificate number505
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMeganet Corporation · website
Software versions4.4.0.0/M145

Module description

Quoted from the NIST CMVP entry for this certificate.

VME Crypto Engine is a suite of tools that make data encryption and decryption easy and reliable. VME Crypto Engine also provides tools that allow you to encrypt and decrypt email messages, chat sessions, files transmitted ftp, and more.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • EMI/EMC: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES77
RSAvendor affirmed
SHA-183
Triple-DES188

Other algorithms

VME

Tested configurations

  • Windows XP Professional Version 2002 SP1. The following operating systems must use the Microsoft® Base Cryptographic Provider validated to FIPS 140-2 under Certificate #238 operating in FIPS mode: Windows 98, Second Edition, Windows ME Build 4.90.3000, Windows NT 4.0 Workstation SP 6, Windows NT 4.0 Server SP 6, Windows 2000 Professional SP4, Windows 2000 Server SP 4, Windows 2000 Advanced Server SP 4, Windows XP Home Edition SP 1, Windows Server 2003 Enterprise Edition (all in single-user mode)

Validation history

DateTypeLab
2005-01-24InitialUL Verification Services, Inc.
2005-02-04Update
2005-05-04Update
2007-12-07Update

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: 2005-01-24, 2005-02-04, 2005-05-04, 2007-12-07

Source documents