808bits

Secure Kernel Code Integrity

FIPS 140-2 certificate #3096 · Microsoft Corporation · data as of 2026-10-21

Secure Kernel Code Integrity, from Microsoft Corporation, holds FIPS 140-2 certificate #3096 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 #3090. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with modules Windows OS Loader validated to FIPS 140-2 under Cert. #3090, #3194 or #3480 operating in FIPS mode or Windows Resume validated to FIPS 140-2 under Cert. #3091 operating in FIPS mode

Certificate

Certificate number3096
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorMicrosoft Corporation · website
Software versions10.0.15063 [1], 10.0.16299 [2] and 10.0.17134 [3]

Module description

Quoted from the NIST CMVP entry for this certificate.

Secure Kernel Code Integrity (SKCI) running in the Virtual Secure Mode (VSM) of the Hyper-V hypervisor will only grant execute access to physical pages in the kernel that have been successfully verified. Executable pages will not have write permission outside of Hyper-V. Therefore, only verified code can be executed.

Security level exceptions

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

Approved algorithms (3)

AlgorithmCAVP certificates
AES4624, 4897
RSA2522, 2523, 2668, 2674, 3080, 3081
SHS3790, 4009, 4633

Tested configurations

  • Windows 10 Education April 2018 Update (x64) running on a Microsoft Surface Laptop without PAA [3]
  • Windows 10 Education Creators Update (x64) running on a Microsoft Surface Pro without PAA [1]
  • Windows 10 Education Fall Creators Update (x64) running on a Microsoft Surface Pro without PAA [2]
  • Windows 10 Enterprise April 2018 Update (x64) running on a Microsoft Surface Book 2 without PAA [3]
  • Windows 10 Enterprise April 2018 Update (x64) running on a Microsoft Surface Laptop without PAA [3]
  • Windows 10 Enterprise April 2018 Update (x64) running on a Microsoft Surface Pro LTE without PAA [3]
  • Windows 10 Enterprise April 2018 Update (x64) running on a Microsoft Surface Studio 2 with PAA [3]
  • Windows 10 Enterprise April 2018 Update (x64) running on a Microsoft Surface Studio without PAA [3]
  • Windows 10 Enterprise April 2018 Update (x64) running on an HP Pro x2 612 G2 Detachable PC with LTE without PAA [3]
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Book without PAA [1]
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Laptop without PAA [1]
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Pro 4 without PAA [1]
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Pro without PAA [1]
  • Windows 10 Enterprise Creators Update (x64) running on a Microsoft Surface Studio without PAA [1]
  • Windows 10 Enterprise Creators Update (x64) running on an HP Pro x2 612 G2 Detachable PC with LTE without PAA [1]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Book 2 without PAA [2]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Book without PAA [2]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Laptop without PAA [2]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Pro 4 without PAA [2]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Pro without PAA [2]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Studio without PAA [2]
  • Windows 10 Enterprise Fall Creators Update (x64) running on an HP Pro x2 612 G2 Detachable PC with LTE without PAA [2]
  • Windows 10 Pro April 2018 Update (x64) running on a Dell Latitude 12 Rugged Tablet without PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on a Dell Latitude 5290 without PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on a Microsoft Surface Book 2 without PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on a Microsoft Surface Go without PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on a Microsoft Surface Laptop 2 with PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on a Microsoft Surface Laptop without PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on a Microsoft Surface Pro 6 with PAA [3] (single-user mode)
  • Windows 10 Pro April 2018 Update (x64) running on a Microsoft Surface Pro LTE without PAA [3]
  • Windows 10 Pro April 2018 Update (x64) running on an HP Slimline Desktop with PAA [3]
  • Windows 10 Pro Creators Update (x64) on Hyper-V on Windows Server 2016 running on a Surface Pro 4 without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Dell Latitude 5285 without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Dell PowerEdge R630 Server without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Dell Precision Tower 5810MT without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface Laptop without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface Pro 3 without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Microsoft Surface Pro without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on a Panasonic Toughbook without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on an HP Compaq Pro 6305 without PAA [1]
  • Windows 10 Pro Creators Update (x64) running on an HP Slimline Desktop with PAA [1]
  • Windows 10 Pro Fall Creators Update (x64) on Hyper-V on Windows Server 2016 running on a Surface Pro 4 without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell Latitude 5285 without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell Latitude 5290 without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell PowerEdge R630 Server without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell Precision Tower 5810MT without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface Laptop without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface Pro 3 without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface Pro without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on a Panasonic Toughbook without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on an HP Compaq Pro 6305 without PAA [2]
  • Windows 10 Pro Fall Creators Update (x64) running on an HP Slimline Desktop with PAA [2]
  • Windows 10 S Creators Update (x64) running on a Microsoft Surface Laptop without PAA [1]
  • Windows 10 S Fall Creators Update (x64) running on a Microsoft Surface Laptop without PAA [2]
  • Windows Server Datacenter Core (x64) on Hyper-V on Windows Server running on a Dell Precision Tower 5810MT without PAA [2][3]
  • Windows Server Datacenter Core (x64) running on a Dell PowerEdge R630 Server without PAA [2]
  • Windows Server Datacenter Core (x64) running on a Dell PowerEdge R740 Server without PAA [2][3]
  • Windows Server Datacenter Core (x64) running on a Dell Precision Tower 5810MT without PAA [2]
  • Windows Server Standard Core (x64) on Hyper-V on Windows Server 2016 running on a Dell PowerEdge R740 Server without PAA [3]
  • Windows Server Standard Core (x64) on Hyper-V on Windows Server running on a Dell Precision Tower 5810MT without PAA [2][3]
  • Windows Server Standard Core (x64) running on a Dell PowerEdge R630 Server without PAA [2]
  • Windows Server Standard Core (x64) running on a Dell PowerEdge R740 Server without PAA [2][3]
  • Windows Server Standard Core (x64) running on a Dell Precision Tower 5810MT without PAA [2]

Validation history

DateTypeLab
2018-04-11InitialLeidos Accredited Testing & Evaluation (AT&E) Lab
2018-10-16UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2019-07-15UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2019-08-27UpdateLeidos 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-04-11, 2018-10-16, 2019-07-15, 2019-08-27

Source documents