808bits

Windows 7 Code Integrity (ci.dll)

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

Windows 7 Code Integrity (ci.dll), from Microsoft Corporation, holds FIPS 140-2 certificate #1327 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 dependency on certificate #1326. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with Windows 7 Winload OS Loader (winload.exe) validated to FIPS 140-2 under Cert. #1326 operating in FIPS mode

Certificate

Certificate number1327
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMicrosoft Corporation · website
Software versions6.1.7600.16385, 6.1.7600.17122, 6.1.7600.21320, 6.1.7601.17514, 6.1.7601.17950 and 6.1.7601.22108

Module description

Quoted from the NIST CMVP entry for this certificate.

This is a dynamically linked library that runs as ntoskrnl.exe. It verifies the integrity of executable files, including kernel mode drivers, critical system components and user mode crypto modules, before these files are loaded from disk into memory by the memory manager.

Approved algorithms (2)

AlgorithmCAVP certificates
RSA557
SHS1081

Other algorithms

MD5

Tested configurations

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

Validation history

DateTypeLab
2010-06-15InitialSAIC-VA
2011-06-01UpdateSAIC-VA
2013-01-24UpdateSAIC-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-06-15, 2011-06-01, 2013-01-24

Source documents