808bits

Microsoft Windows Server 2008 R2 Cryptographic Primitives Library (bcryptprimitives.dll)

FIPS 140-2 certificate #1336 · Microsoft Corporation · data as of 2026-08-28
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 Windows Server 2008 R2 Code Integrity (ci.dll) validated to FIPS 140-2 under Cert. #1334 operating in FIPS mode

Certificate

Certificate number1336
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMicrosoft Corporation · website
Software versions6.1.7600.16385 or 6.1.7601.17514

Module description

BCRYPT.DLL provides cryptographic services, through its documented interfaces, to Windows components and applications running on Windows. The cryptographic module, bcryptprimitives.dll, encapsulates several different cryptographic algorithms in an easy-to-use cryptographic module accessible via the Microsoft CNG (Cryptography, Next Generation) API. It can be dynamically linked into applications by software developers to permit the use of general-purpose FIPS 140-2 compliant cryptography.

Approved algorithms

AlgorithmCAVP certificate
AES1168, 1187
AES GCM1168
AES GMAC1168
DRBG23, 27
DSA391
ECDSA142
HMAC686
KASvendor affirmed
RNG649
RSA559, 567
SHS1081
Triple-DES846

Other algorithms

AES (Cert. #1168, key wrapping; key establishment methodology provides between 128 and 256 bits of encryption strength); DES; HMAC MD5; MD2; MD4; MD5; RC2; RC4

Tested configurations

  • Microsoft Windows Server 2008 R2 (IA64 version)
  • Microsoft Windows Server 2008 R2 (x64 Version)
  • Microsoft Windows Server 2008 R2 SP1 (IA64 version) (single-user mode)
  • Microsoft Windows Server 2008 R2 SP1 (x64 version)

Validation history

DateTypeLab
2010-08-12InitialSAIC-VA
2011-06-01UpdateSAIC-VA
2011-06-21UpdateSAIC-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: 2010-08-12, 2011-06-01, 2011-06-21

Source documents