808bits

Windows Vista Enhanced Cryptographic Provider (RSAENH)

FIPS 140-2 certificate #893 · Microsoft Corporation · data as of 2026-09-08

Windows Vista Enhanced Cryptographic Provider (RSAENH), from Microsoft Corporation, holds FIPS 140-2 certificate #893 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. 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 with Code Integrity (ci.dll) validated to FIPS 140-2 under Cert. #890 operating in FIPS mode

Certificate

Certificate number893
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMicrosoft Corporation · website
Software versions6.0.6000.16386

Module description

Quoted from the NIST CMVP entry for this certificate.

RSAENH encapsulates several different cryptographic algorithms in an easy-to-use cryptographic module accessible via the Microsoft CryptoAPI. Developers dynamically link the Microsoft RSAENH module into their applications to provide FIPS 140-2 compliant cryptographic support.

Approved algorithms (6)

AlgorithmCAVP certificates
AES553
HMAC297
RNG321
RSA255, 258
SHS618
Triple-DES549

Other algorithms

DES; MD2; MD4; MD5; RC2; RC4; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Microsoft Windows Vista Ultimate Edition (x64 version) (single-user mode)
  • Microsoft Windows Vista Ultimate Edition (x86 Version)

Validation history

DateTypeLab
2008-01-10InitialSAIC-VA

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: 2008-01-10

Source documents