Kernel-mode code signing and integrity

Code signing and integrity at a glance

To ensure that Windows files are trustworthy and haven't been tampered with, the Windows code integrity process verifies the signature of each file that runs in the Windows kernel. On systems enforcing Smart App Control or an App Control for Business policy, Windows extends code integrity verification to every user mode binary that runs as well. Code signing is core to establishing the integrity of firmware, drivers, and software across the Windows platform. Code signing creates a digital signature by encrypting the hash of the file with the private key from a code-signing certificate and embedding that signature into the file or a catalog of signatures. The Windows code integrity process verifies the integrity of the signed file by comparing its hash to the signed hash, and confirms that the signer is a reputable publisher.

The Windows environment evaluates the digital signature on Windows boot code, Windows kernel code, and Windows user mode applications. Before code integrity runs, Secure Boot verifies the signature on bootloaders, Option ROMs, and other boot components to ensure that the files are unmodified and come from a trusted and reputable publisher. For drivers that Microsoft doesn't publish, Kernel mode code integrity verifies the signature on kernel drivers and requires that drivers be signed by Windows or certified by the Windows Hardware Compatibility Program (WHCP). This program ensures that third-party drivers are compatible with various hardware and Windows and that the drivers are from vetted driver developers.

Learn more