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
This is by far the biggest update to the WDACConfig module. It brings a lot of new features, improvements, and changes to the cmdlets. The main focus of this update is to make the workflow of the cmdlets more user-friendly, faster, and more efficient. There are some inevitable breaking changes along with new features and improvements that are all listed below.
✅ Lots of new guides have been added
✅Previous guides have been all updated to reflect the new changes
📽️ New videos with voice overs have been provided
Introducing Sandboxing-like Capability For The Installed Programs
The vast majority of programs incorporate Dynamic Link Libraries (DLLs) and additional dependencies such as .com, .rll, .ocx, .msp, .mst, .bin, .hxs, .mui, .lex, .mof etc., which are replicated into their designated installation directory throughout the setup phase. These critical files may harbor security flaws susceptible to exploitation by malware. To counteract this, the innovative feature establishes a sandbox-like perimeter encircling the application's dependencies. This ensures that solely the application's own executables have the privilege to interact with the DLLs and dependency files, effectively barring all other executables from accessing them.
This feature is available in the Edit-WDACConfig and Edit-SignedWDACConfig cmdlets. It can be activated using the -BoostedSecurity parameter.
This feature might be added to other cmdlets as well after further evaluations.
Removed -AllowNewAppsAuditEvents parameters from both cmdlets, its job has been merged with -AllowNewApps parameter. This simplifies the workflow as you no longer have to make a decision between which parameter to use when you need to allow apps or files.
The -AllowNewApps parameter now automatically detects the files run during audit mode from event logs and display them to you in a GUI, offering you the option to include them in the supplemental policy by providing comprehensive details about every detected file and empowering you to make informed decision about them. It also checks for kernel-protected files in the logs you select, such as the main executable of the Xbox games, and allows them in the supplemental policy based on PFN (Package Family Name).
The SnapBack security mechanism is triggered sooner, restoring the base policy that is in audit mode back to enforced mode as soon as possible.
Using parallel processing methods, the workflow of the cmdlet has been optimized for faster execution.
You can now use the -AllowNewApps parameter either by selecting directories to scan, purely rely on audit event logs or both. Previously, the workflow would require you to select directories to scan and would fail otherwise. Now you can solely rely on audit event logs to allow new apps or files, or if you want to allow a new file but you don't know its exact location.
The -UpdateBasePolicy parameter has been upgraded. It now intelligently increases the version number of the base policy, ensuring that the new version is always one version higher than the previous one. The version change considers all semantic versioning rules such as revision, build, minor and major numbers and their maximum allowed values.
Set-CiRuleOptions
It's a new cmdlet, consider it an improved version of the built-in cmdlet Set-RuleOption. It offers more features and improvements such as removing or adding rules at the same time in bulk.
Completely internalized policy rule option modifications, no longer using built-in cmdlets. This change results in much faster policy creation.
New-WDACConfig
Complete Overhaul
All of this cmdlets's parameters have been replaced with more user-friendly and efficient ones. No functionality has been lost. The goal is to offer the end-user the ability to quickly and easily choose the desired settings with 0 ambiguity. As a result, the following changes have been made:
Removed the -MakePolicyFromAuditLogs parameter from the cmdlet. Its job can now be done with the -AllowNewApps parameter in the Edit-WDACConfig and Edit-SignedWDACConfig cmdlets, or by the New-SupplementalWDACConfig cmdlet.
New parameter -PolicyType: Use it to create base policies, it offers 3 options: 'DefaultWindows', 'AllowMicrosoft', 'SignedAndReputable'.
New parameter -GetUserModeBlockRules: Use it to download or deploy the latest User Mode Block rules from the Microsoft GitHub repository. The User Mode block rules are no longer coupled with the base policy, they are now deployed as a standalone policy separately, offering greater control over them and their life cycle. This is due to the fact that Windows no longer has a limit on how many WDAC policies can be deployed on the system. Previously the limit was 32 policies.
New parameter -GetDriverBlockRules: Use it to download or deploy the latest Kernel Mode drivers Block rules from the Microsoft website.
New parameter -Audit: Used to turn on audit mode in the base policy. Only available when -PolicyType parameter is used.
New parameter -AutoUpdate: Only available when -GetDriverBlockRules parameter is used. It will automatically update the driver block rules when a new version is available using scheduled task.
Get-CIPolicySetting
Gets the secure settings value from the deployed CI policies using the Windows APIs.
Refer to the following documents for more info:
New parameter OnlySystemPolicies: It will display only the system policies when used.
The version number of the policies are now converted to proper semantic versioning format.
Assert-WDACConfigIntegrity
Added support for the SHA3-512 hashing algorithm that is available beginning Windows 11 24H2.
Other Changes
The ConvertTo-WDACPolicy cmdlet when using local logs as the source, has become faster using high performance functions.
Kernel-protected files are now faster to detect and rules for them are created in better ways.
Sub-modules in each cmdlet are now loaded faster.
Cmdlet outputs are now more streamlined and consistent.
During the module preload phase, certain immutable global variables are established, remaining unalterable for the duration of the session. Previously, these variables were instantiated only if they did not already exist within the session's scope with the same name. Now, the values of these pre-existing variables are scrutinized against those defined within the module. Should a discrepancy arise, an error is triggered. This rigorous validation mechanism ensures the integrity of critical variables, safeguarding them from any potential malicious alterations prior to the module's loading.
Whenever using cmdlets that require interaction with Code Integrity and AppLocker event logs, such as Edit-WDACConfig, Edit-SignedWDACConfig or New-WDACConfig -Audit, the Code Integrity Operational's event log size is evaluated. If the current free capacity is less than 1MB and its maximum size is less than 10MB, its size is increased by 1MB. This is a controlled automated workflow that is introduced in this version that aims to prevent the overwrite of the event logs. You can always use the -LogSize parameter with the cmdlets that support it to set the desired max size for the Code Integrity Operational logs.
Increased the minimum required OS build version from 22621.2428 to 22621.3447. In this build, the cap for the deployed WDAC policies was removed and the redesign of the module is based on that change.
Increased the update check interval from 10 minutes to 30 minutes.
What's New
This is by far the biggest update to the WDACConfig module. It brings a lot of new features, improvements, and changes to the cmdlets. The main focus of this update is to make the workflow of the cmdlets more user-friendly, faster, and more efficient. There are some inevitable breaking changes along with new features and improvements that are all listed below.
Introducing Sandboxing-like Capability For The Installed Programs
The vast majority of programs incorporate Dynamic Link Libraries (DLLs) and additional dependencies such as
.com,.rll,.ocx,.msp,.mst,.bin,.hxs,.mui,.lex,.mofetc., which are replicated into their designated installation directory throughout the setup phase. These critical files may harbor security flaws susceptible to exploitation by malware. To counteract this, the innovative feature establishes a sandbox-like perimeter encircling the application's dependencies. This ensures that solely the application's own executables have the privilege to interact with the DLLs and dependency files, effectively barring all other executables from accessing them.This feature is available in the
Edit-WDACConfigandEdit-SignedWDACConfigcmdlets. It can be activated using the-BoostedSecurityparameter.This feature might be added to other cmdlets as well after further evaluations.
New Video Guides
Cmdlet Changes
Edit-WDACConfig and Edit-SignedWDACConfig
Removed
-AllowNewAppsAuditEventsparameters from both cmdlets, its job has been merged with-AllowNewAppsparameter. This simplifies the workflow as you no longer have to make a decision between which parameter to use when you need to allow apps or files.The
-AllowNewAppsparameter now automatically detects the files run during audit mode from event logs and display them to you in a GUI, offering you the option to include them in the supplemental policy by providing comprehensive details about every detected file and empowering you to make informed decision about them. It also checks for kernel-protected files in the logs you select, such as the main executable of the Xbox games, and allows them in the supplemental policy based on PFN (Package Family Name).The SnapBack security mechanism is triggered sooner, restoring the base policy that is in audit mode back to enforced mode as soon as possible.
Using parallel processing methods, the workflow of the cmdlet has been optimized for faster execution.
You can now use the
-AllowNewAppsparameter either by selecting directories to scan, purely rely on audit event logs or both. Previously, the workflow would require you to select directories to scan and would fail otherwise. Now you can solely rely on audit event logs to allow new apps or files, or if you want to allow a new file but you don't know its exact location.The
-UpdateBasePolicyparameter has been upgraded. It now intelligently increases the version number of the base policy, ensuring that the new version is always one version higher than the previous one. The version change considers all semantic versioning rules such as revision, build, minor and major numbers and their maximum allowed values.Set-CiRuleOptions
It's a new cmdlet, consider it an improved version of the built-in cmdlet
Set-RuleOption. It offers more features and improvements such as removing or adding rules at the same time in bulk.Completely internalized policy rule option modifications, no longer using built-in cmdlets. This change results in much faster policy creation.
New-WDACConfig
Complete Overhaul
All of this cmdlets's parameters have been replaced with more user-friendly and efficient ones. No functionality has been lost. The goal is to offer the end-user the ability to quickly and easily choose the desired settings with 0 ambiguity. As a result, the following changes have been made:
Removed the
-MakePolicyFromAuditLogsparameter from the cmdlet. Its job can now be done with the-AllowNewAppsparameter in theEdit-WDACConfigandEdit-SignedWDACConfigcmdlets, or by the New-SupplementalWDACConfig cmdlet.New parameter
-PolicyType: Use it to create base policies, it offers 3 options: 'DefaultWindows', 'AllowMicrosoft', 'SignedAndReputable'.New parameter
-GetUserModeBlockRules: Use it to download or deploy the latest User Mode Block rules from the Microsoft GitHub repository. The User Mode block rules are no longer coupled with the base policy, they are now deployed as a standalone policy separately, offering greater control over them and their life cycle. This is due to the fact that Windows no longer has a limit on how many WDAC policies can be deployed on the system. Previously the limit was 32 policies.New parameter
-GetDriverBlockRules: Use it to download or deploy the latest Kernel Mode drivers Block rules from the Microsoft website.New parameter
-Audit: Used to turn on audit mode in the base policy. Only available when-PolicyTypeparameter is used.New parameter
-AutoUpdate: Only available when-GetDriverBlockRulesparameter is used. It will automatically update the driver block rules when a new version is available using scheduled task.Get-CIPolicySetting
Gets the secure settings value from the deployed CI policies using the Windows APIs. Refer to the following documents for more info:
Confirm-WDACConfig
OnlySystemPolicies: It will display only the system policies when used.Assert-WDACConfigIntegrity
Other Changes
The ConvertTo-WDACPolicy cmdlet when using local logs as the source, has become faster using high performance functions.
Kernel-protected files are now faster to detect and rules for them are created in better ways.
Sub-modules in each cmdlet are now loaded faster.
Cmdlet outputs are now more streamlined and consistent.
During the module preload phase, certain immutable global variables are established, remaining unalterable for the duration of the session. Previously, these variables were instantiated only if they did not already exist within the session's scope with the same name. Now, the values of these pre-existing variables are scrutinized against those defined within the module. Should a discrepancy arise, an error is triggered. This rigorous validation mechanism ensures the integrity of critical variables, safeguarding them from any potential malicious alterations prior to the module's loading.
Whenever using cmdlets that require interaction with Code Integrity and AppLocker event logs, such as
Edit-WDACConfig,Edit-SignedWDACConfigorNew-WDACConfig -Audit, the Code Integrity Operational's event log size is evaluated. If the current free capacity is less than 1MB and its maximum size is less than 10MB, its size is increased by 1MB. This is a controlled automated workflow that is introduced in this version that aims to prevent the overwrite of the event logs. You can always use the-LogSizeparameter with the cmdlets that support it to set the desired max size for the Code Integrity Operational logs.Increased the minimum required OS build version from
22621.2428to22621.3447. In this build, the cap for the deployed WDAC policies was removed and the redesign of the module is based on that change.Increased the update check interval from 10 minutes to 30 minutes.