Harden Windows Safely, Securely using Official Supported Microsoft methods and proper explanation | Always up-to-date and works with the latest build of Windows | Provides tools and Guides for Personal, Enterprise, Government and Military security levels | Read The Rationale https://github.com/HotCakeX/Harden-Windows-Security/blob/main/Rationale.md
Added new parameter to ConvertTo-WDACPolicy called -SuppPolicyName which allows the user to define a custom name for the supplemental policy. If not defined, the module will continue to automatically generate a name based on the source type and date + time.
In Edit-WDACConfig and Edit-SignedWDACConfig cmdlets for the -AllowNewApps parameter, the directory paths that the user selects are de-duplicated now so if you accidentally select the same directory multiple times using the GUI, the module only performs a single scan, saving time and reducing redundancy.
Again in Edit-WDACConfig and Edit-SignedWDACConfig cmdlets for the -AllowNewApps parameter, a new parallel task has been added to check for files signed with ECC algorithms, the module will create hash level rules for those files. This is because WDAC only supports files signed with RSA algorithm and even though ECC signed files have Signature based rules created for them in the XML policy, they are still not authorized to run and generate VerificationError 23 in the Code Integrity Operational event logs.
Since this new check runs in the background simultaneously, it doesn't prolong the execution flow.
Fixed AppLocker logs property alignments. Also the ConvertTo-WDACPolicy cmdlet now shows the source of the log in extreme visibility mode, so you can know whether a file was logged in AppLocker logs or Code Integrity operational logs.
Improved the accuracy of the boosted security modes, also known as dependency sandboxing. They are now processed faster and also created for files that were run during installing or audit phase but are no longer on the disk.
Improved the speed of Code Integrity and AppLocker logs parsing yet again.
What's New
Added new parameter to ConvertTo-WDACPolicy called
-SuppPolicyNamewhich allows the user to define a custom name for the supplemental policy. If not defined, the module will continue to automatically generate a name based on the source type and date + time.In Edit-WDACConfig and Edit-SignedWDACConfig cmdlets for the
-AllowNewAppsparameter, the directory paths that the user selects are de-duplicated now so if you accidentally select the same directory multiple times using the GUI, the module only performs a single scan, saving time and reducing redundancy.Again in Edit-WDACConfig and Edit-SignedWDACConfig cmdlets for the
-AllowNewAppsparameter, a new parallel task has been added to check for files signed with ECC algorithms, the module will create hash level rules for those files. This is because WDAC only supports files signed with RSA algorithm and even though ECC signed files have Signature based rules created for them in the XML policy, they are still not authorized to run and generate VerificationError 23 in the Code Integrity Operational event logs.Fixed AppLocker logs property alignments. Also the
ConvertTo-WDACPolicycmdlet now shows the source of the log in extreme visibility mode, so you can know whether a file was logged in AppLocker logs or Code Integrity operational logs.Improved the accuracy of the boosted security modes, also known as dependency sandboxing. They are now processed faster and also created for files that were run during installing or audit phase but are no longer on the disk.
Improved the speed of Code Integrity and AppLocker logs parsing yet again.