Secure Kernel Code Integrity
Secure Kernel Code Integrity, from Microsoft Corporation, holds FIPS 140-2 certificate #4640 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode with module Windows OS Loader validated to FIPS 140-2 under Cert. #4545 operating in FIPS mode
Certificate
| Certificate number | 4640 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Microsoft Corporation · website |
| Software versions | 10.0.17763.10021 and 10.0.17763.10127 |
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 (2)
Tested configurations
- Windows Server 2019 Datacenter Core (x64) running on a Dell PowerEdge R640 Server with an Intel Xeon Gold 6230
- Windows Server 2019 Datacenter Core (x64) running on a Dell PowerEdge R840 Server with an Intel Xeon Platinum 8260
- Windows Server 2019 Datacenter Core (x64) running on a Dell XR2 with an Intel Xeon Silver 4114
- Windows Server 2019 Datacenter Core (x64) running on a Rugged Mobile Appliance with an Intel Xeon D-1559 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-10-23 | Initial | Leidos 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2023-10-23