808bits

Windows Server 2003 Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH)

FIPS 140-2 certificate #875 · Microsoft Corporation · data as of 2026-09-03

Windows Server 2003 Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH), from Microsoft Corporation, holds FIPS 140-2 certificate #875 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

Certificate

Certificate number875
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMicrosoft Corporation · website
Software versions5.2.3790.3959

Module description

Quoted from the NIST CMVP entry for this certificate.

The Windows Server 2003 Enhanced DSS and Diffie-Hellman Cryptographic Provider (DSSENH) is a FIPS 140-2 compliant, software-based, cryptographic module. DSSENH encapsulates several different cryptographic algorithms (including SHA-1, 3DES, DSA and Diffie-Hellman) in a cryptographic module accessible via the Microsoft CryptoAPI (CAPI).

Approved algorithms (5)

AlgorithmCAVP certificates
DSA221
RNG314
RSA245
SHS611
Triple-DES543

Other algorithms

DES; DES40; Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); MD5; RC2; RC4

Tested configurations

  • Windows Server 2003 Service Pack 2 (x86, x64 and IA64) (single-user mode)

Validation history

DateTypeLab
2007-11-30InitialSAIC-VA
2007-12-18Update

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: 2007-11-30, 2007-12-18

Source documents