From 44c2e6bf787dd02dca24e18db66e7e0af3e60aad Mon Sep 17 00:00:00 2001
From: cchavez-msft <136099320+cchavez-msft@users.noreply.github.com>
Date: Thu, 11 Jul 2024 10:47:47 -0400
Subject: [PATCH] HardwareSecurityJeffreySutherland

---
 .../book/hardware-security-silicon-assisted-security.md         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/book/hardware-security-silicon-assisted-security.md b/windows/security/book/hardware-security-silicon-assisted-security.md
index 707bb1ea4e..204e36cebf 100644
--- a/windows/security/book/hardware-security-silicon-assisted-security.md
+++ b/windows/security/book/hardware-security-silicon-assisted-security.md
@@ -28,7 +28,7 @@ Since more privileged VTLs can enforce their own memory protections, higher VTLs
 
 **Hypervisor-enforced Paging Translation (HVPT)**, overall security enhancement for the system. protects linear address translations from being tampered with
 
-**Hypervisor-protected code integrity (HVCI)**, also called memory integrity, uses VBS to run Kernel Mode Code Integrity (KMCI) inside the secure VBS environment instead of the main Windows kernel. This helps prevent attacks that attempt to modify kernel-mode code for things like drivers. The KMCI checks that all kernel code is properly signed and hasn't been tampered with before it is allowed to run. HVCI ensures that only validated code can be executed in kernel mode. The hypervisor leverages processor virtualization extensions to enforce memory protections that prevent kernel-mode software from executing code that has not been first validated by the code integrity subsystem. HVCI protects against common attacks like WannaCry that rely on the ability to inject malicious code into the kernel. HVCI can prevent injection of malicious kernel-mode code even when drivers and other kernel-mode software have bugs.
+**Memory integrity**, also called Hypervisor-protected code integrity (HVCI), uses VBS to run Kernel Mode Code Integrity (KMCI) inside the secure VBS environment instead of the main Windows kernel. This helps prevent attacks that attempt to modify kernel-mode code for things like drivers. The KMCI checks that all kernel code is properly signed and hasn't been tampered with before it is allowed to run. Memory integrity ensures that only validated code can be executed in kernel mode. The hypervisor leverages processor virtualization extensions to enforce memory protections that prevent kernel-mode software from executing code that has not been first validated by the code integrity subsystem. Memory integrity protects against common attacks like WannaCry that rely on the ability to inject malicious code into the kernel. Memory integrity can prevent injection of malicious kernel-mode code even when drivers and other kernel-mode software have bugs.
 
 With new installs of Windows 11, OS support for VBS and HVCI is turned on by default for all devices that meet prerequisites.