808bits

Cryptographic Primitives Library

FIPS 140-2 certificate #3095 · Microsoft Corporation · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with modules Kernel Mode Cryptographic Primitives Library validated to FIPS 140-2 under Cert. #3094 operating in FIPS mode and Code Integrity validated to FIPS 140-2 under Cert. #3093 operating in FIPS mode or Secure Kernel Code Integrity validated to FIPS 140-2 under Cert. #3096 operating in FIPS mode

Certificate

Certificate number3095
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorMicrosoft Corporation · website
Software versions10.0.15063

Module description

The Cryptographic Primitives Library (bcryptprimitives.dll and ncryptsslp.dll) provides cryptographic services to Windows components and applications. It includes cryptographic algorithms in an easy-to-use cryptographic module via the Cryptography Next Generation (CNG) API. It can be dynamically linked into applications for the use of general-purpose FIPS 140-2 validated cryptography.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 2

Approved algorithms

AlgorithmCAVP certificate
AES4624
CKGvendor affirmed
CVL1278, 1281
DRBG1555
DSA1223
ECDSA1133
HMAC3061
KAS127
KBKDF140
KTS
PBKDFvendor affirmed
RSA2521, 2522
SHS3790
Triple-DES2459

Allowed algorithms

HMAC-MD5; MD5; NDRNG

Tested configurations

  • Surface Hub (x64) running on a Microsoft Surface Hub with PAA
  • Windows 10 Education Creators Update (x64) running on a Microsoft Surface Pro with PAA
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface 3 with PAA
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Book with PAA
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Laptop with PAA
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Pro 4 with PAA
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Pro with PAA
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Studio with PAA
  • Windows 10 Enterprise Creators Update (x64) running on an HP Pro x2 612 G2 Detachable PC with LTE with PAA
  • Windows 10 Home Creators Update (x86) running on a Dell Inspiron 660s without PAA
  • Windows 10 Mobile Creators Update (ARMv7) running on a Microsoft Lumia 650
  • Windows 10 Mobile Creators Update (ARMv7) running on a Microsoft Lumia 950
  • Windows 10 Mobile Creators Update (ARMv7) running on a Microsoft Lumia 950 XL
  • Windows 10 Mobile Creators Update (ARMv7) running on an HP Elite x3
  • Windows 10 Pro Creators Update (x64) on Hyper-V on Windows Server 2016 running on a Surface Pro 4 with PAA
  • Windows 10 Pro Creators Update (x64) running on a Dell Latitude 5285 with PAA
  • Windows 10 Pro Creators Update (x64) running on a Dell PowerEdge R630 Server with PAA
  • Windows 10 Pro Creators Update (x64) running on a Dell Precision Tower 5810MT with PAA
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface 3 with LTE with PAA
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface Laptop with PAA
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface Pro 3 with PAA
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface Pro with PAA
  • Windows 10 Pro Creators Update (x64) running on a Panasonic Toughbook with PAA (single-user mode)
  • Windows 10 Pro Creators Update (x64) running on an HP Compaq Pro 6305 with PAA
  • Windows 10 Pro Creators Update (x64) running on an HP Slimline Desktop with PAA
  • Windows 10 S Creators Update (x64) running on a Microsoft Surface Laptop with PAA

Validation history

DateTypeLab
2018-03-22InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2018-03-22

Source documents