From 3b311cfdcdbf7271b25546c170ebbee851ec87c2 Mon Sep 17 00:00:00 2001 From: jsuther1974 Date: Wed, 2 Nov 2022 13:02:40 -0700 Subject: [PATCH] Update script-enforcement.md --- .../design/script-enforcement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md b/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md index f3d0be7276..a33a5ba8e1 100644 --- a/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md +++ b/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md @@ -64,7 +64,7 @@ If any WDAC policy is active that enables script enforcement, even if that polic ### COM objects -WDAC additionally enforces a restricted allowlist for COM objects that can be expanded or further restricted by your WDAC policy. For more information on how to allow or deny COM objects, see [Allow COM object registration](/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy). +WDAC additionally enforces a restricted allowlist for COM objects that can be expanded or further restricted by your WDAC policy. COM object enforcement **isn't** affected by option **11 Disabled:Script Enforcement**. For more information on how to allow or deny COM objects, see [Allow COM object registration](/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy). ## Scripts that aren't directly controlled by WDAC