-
Notifications
You must be signed in to change notification settings - Fork 160
New SupplementalWDACConfig
-
Mandatory parameters indicate you always need to provide values for them.
-
Automatic parameters indicate that if you used Set-CommonWDACConfig cmdlet to set default values for them, the module will automatically use them. This saves time and prevents repetitive tasks. However, if no value exists in User Configurations for an Automatic parameter and you didn't explicitly provide a value for that parameter either, then you will see an error asking you to provide value for it. Explicitly providing a value for an Automatic parameter in the command line overrides its default value in User Configurations, meaning the module will ignore the value of the same parameter in the User Configurations file.
-
Optional parameters indicate that they are not required and without using them the module will automatically run with the optimal settings.
-
Many cmdlets and parameters of the module support the PowerShell's built-in
-Debug
switch and when that switch is used, they display extra details and debugging messages on the console, showing you what's happening under the hood.
New-SupplementalWDACConfig [-Normal] -ScanLocation <String> -SuppPolicyName <String> -PolicyPath <String>
[-Deploy] [-SpecificFileNameLevel <String>] [-NoUserPEs] [-NoScript] [-Level <String>]
[-Fallbacks <String[]>]
Creates a normal Supplemental policy for a base policy.
-
-ScanLocation <String>
: The directory or drive that you want to scan for files that will be allowed to run by the Supplemental policy. -
-SuppPolicyName <String>
: Add a descriptive name for the Supplemental policy. Accepts only alphanumeric and space characters.
-
-PolicyPath <String>
: Browse for the xml file of the Base policy this Supplemental policy is going to expand. Supports tab completion by showing only.xml
files with Base Policy Type.
-
-Deploy
: Indicates that the module will automatically deploy the Supplemental policy after creation. -
-Levels <String>
: Offers the same official Levels for scanning of the specified directory path. If no level is specified the default, which is set to FilePublisher in this module, will be used. -
-Fallbacks <String[]>
: Offers the same official Fallbacks for scanning of the specified directory path. If no fallbacks is specified the default, which is set to Hash in this module, will be used. -
-SpecificFileNameLevel
: You can choose one of the following options: "OriginalFileName", "InternalName", "FileDescription", "ProductName", "PackageFamilyName", "FilePath". More info available on Microsoft Learn -
-NoUserPEs
: By default the module includes user PEs in the scan, but when you use this switch parameter, they won't be included. More info available on Microsoft Learn -
-NoScript
: More info available on Microsoft Learn
- SupplementalPolicy
<Custom Name>
.xml - {GUID}.cip
New-SupplementalWDACConfig [-FilePathWildCards] -WildCardPath <String> -SuppPolicyName <String> -PolicyPath
<String> [-Deploy]
Creates a Supplemental policy that allows a file path that includes one or more wildcard *
character in it.
-
-WildCardPath
: A file path that includes at least one wildcard*
character and ends with a\
. -
-SuppPolicyName <String>
: Add a descriptive name for the Supplemental policy. Accepts only alphanumeric and space characters.
-
-PolicyPath
: Browse for the xml file of the Base policy this Supplemental policy is going to expand. Supports tab completion by showing only.xml
files with Base Policy Type.
-
-Deploy
: Indicates that the module will automatically deploy the Supplemental policy after creation.
- SupplementalPolicy
<Custom Name>
.xml - {GUID}.cip
New-SupplementalWDACConfig [-InstalledAppXPackages] -PackageName <String> -SuppPolicyName <String> -PolicyPath
<String> [-Deploy]
Creates a Supplemental policy based on the package name of an installed app.
More information at Microsoft Learn
-
-PackageName
: Enter the package name of an installed app. Supports wildcard*
character. e.g,*Edge*
or"*Microsoft*"
. -
-SuppPolicyName <String>
: Add a descriptive name for the Supplemental policy. Accepts only alphanumeric and space characters.
-
-PolicyPath
: Browse for the xml file of the Base policy this Supplemental policy is going to expand. Supports tab completion by showing only.xml
files with Base Policy Type.
-
-Deploy
: Indicates that the module will automatically deploy the Supplemental policy after creation.
- SupplementalPolicy
<Custom Name>
.xml - {GUID}.cip
- Create AppControl Policy
- Create Supplemental Policy
- System Information
- Configure Policy Rule Options
- Simulation
- Allow New Apps
- Build New Certificate
- Create Policy From Event Logs
- Create Policy From MDE Advanced Hunting
- Merge App Control Policies
- Deploy App Control Policy
- Get Code Integrity Hashes
- Get Secure Policy Settings
- Update
- Introduction
- App Control for Lightly Managed Devices
- App Control for Fully managed device - Variant 1
- App Control for Fully managed device - Variant 2
- App Control for Fully managed device - Variant 3
- App Control for Fully managed device - Variant 4
- App Control Notes
- How to Create and Deploy a Signed App Control Policy
- Fast and Automatic Microsoft Recommended Driver Block Rules updates
- App Control policy for BYOVD Kernel mode only protection
- EKUs in App Control for Business Policies
- App Control Rule Levels Comparison and Guide
- Script Enforcement and PowerShell Constrained Language Mode in App Control Policies
- How to Use Microsoft Defender for Endpoint Advanced Hunting With App Control
- App Control Frequently Asked Questions (FAQs)
- New-WDACConfig
- New-SupplementalWDACConfig
- Remove-WDACConfig
- Edit-WDACConfig
- Edit-SignedWDACConfig
- Deploy-SignedWDACConfig
- Confirm-WDACConfig
- New-DenyWDACConfig
- Set-CommonWDACConfig
- New-KernelModeWDACConfig
- Get-CommonWDACConfig
- Remove-CommonWDACConfig
- Assert-WDACConfigIntegrity
- Test-CiPolicy
- Get-CiFileHashes
- Get-CIPolicySetting
- Create Bootable USB flash drive with no 3rd party tools
- Event Viewer
- Group Policy
- How to compact your OS and free up extra space
- Hyper V
- Overrides for Microsoft Security Baseline
- Git GitHub Desktop and Mandatory ASLR
- Signed and Verified commits with GitHub desktop
- About TLS, DNS, Encryption and OPSEC concepts
- Things to do when clean installing Windows
- Comparison of security benchmarks
- BitLocker, TPM and Pluton | What Are They and How Do They Work
- How to Detect Changes in User and Local Machine Certificate Stores in Real Time Using PowerShell
- Cloning Personal and Enterprise Repositories Using GitHub Desktop
- Only a Small Portion of The Windows OS Security Apparatus
- Rethinking Trust: Advanced Security Measures for High‐Stakes Systems
- Clean Source principle, Azure and Privileged Access Workstations
- How to Securely Connect to Azure VMs and Use RDP
- Basic PowerShell tricks and notes
- Basic PowerShell tricks and notes Part 2
- Basic PowerShell tricks and notes Part 3
- Basic PowerShell tricks and notes Part 4
- Basic PowerShell tricks and notes Part 5
- How To Access All Stream Outputs From Thread Jobs In PowerShell In Real Time
- PowerShell Best Practices To Follow When Coding
- How To Asynchronously Access All Stream Outputs From Background Jobs In PowerShell
- Powershell Dynamic Parameters and How to Add Them to the Get‐Help Syntax
- RunSpaces In PowerShell
- How To Use Reflection And Prevent Using Internal & Private C# Methods in PowerShell