Update use-signed-policies-to-protect-windows-defender-application-control-against-tampering.md

This commit is contained in:
Denise Vangel-MSFT
2022-06-27 16:15:49 -07:00
committed by GitHub
parent a80d6df2e9
commit 9b6f93fda9

View File

@ -14,7 +14,7 @@ author: jsuther1974
ms.reviewer: isbrahm ms.reviewer: isbrahm
ms.author: dansimp ms.author: dansimp
manager: dansimp manager: dansimp
ms.date: 05/03/2018 ms.date: 06/27/2022
ms.technology: windows-sec ms.technology: windows-sec
--- ---
@ -111,4 +111,4 @@ If you do not have a code signing certificate, see [Optional: Create a code sign
9. Validate the signed file. When complete, the commands should output a signed policy file called {PolicyID}.cip to your desktop. You can deploy this file the same way you deploy an enforced or non-enforced policy. For information about how to deploy WDAC policies, see [Deploy and manage Windows Defender Application Control with Group Policy](deploy-windows-defender-application-control-policies-using-group-policy.md). 9. Validate the signed file. When complete, the commands should output a signed policy file called {PolicyID}.cip to your desktop. You can deploy this file the same way you deploy an enforced or non-enforced policy. For information about how to deploy WDAC policies, see [Deploy and manage Windows Defender Application Control with Group Policy](deploy-windows-defender-application-control-policies-using-group-policy.md).
> [!NOTE] > [!NOTE]
> The device with the signed policy must be rebooted one time with Secure Boot enabled for the UEFI lock to be set. > The device with the signed policy must be rebooted one time with Secure Boot enabled for the UEFI lock to be set.