-
Notifications
You must be signed in to change notification settings - Fork 142
ConvertTo WDACPolicy
ConvertTo-WDACPolicy
[-PolicyToAddLogsTo <FileInfo>]
[-Source <String>]
[-SuppPolicyName <String>]
[-Level <String>]
[-MDEAHLogs <FileInfo[]>]
[-EVTXLogs <FileInfo[]>]
[-FilterByPolicyNames <String[]>]
[-TimeSpan <String>]
[-TimeSpanAgo <UInt64>]
[-KernelModeOnly]
[-LogType <String>]
[-Deploy]
[-ExtremeVisibility]
[<CommonParameters>]
ConvertTo-WDACPolicy
[-BasePolicyFile <FileInfo>]
[-Source <String>]
[-SuppPolicyName <String>]
[-Level <String>]
[-MDEAHLogs <FileInfo[]>]
[-EVTXLogs <FileInfo[]>]
[-FilterByPolicyNames <String[]>]
[-TimeSpan <String>]
[-TimeSpanAgo <UInt64>]
[-KernelModeOnly]
[-LogType <String>]
[-Deploy]
[-ExtremeVisibility]
[<CommonParameters>]
ConvertTo-WDACPolicy
[-BasePolicyGUID <Guid>]
[-Source <String>]
[-SuppPolicyName <String>]
[-Level <String>]
[-MDEAHLogs <FileInfo[]>]
[-EVTXLogs <FileInfo[]>]
[-FilterByPolicyNames <String[]>]
[-TimeSpan <String>]
[-TimeSpanAgo <UInt64>]
[-KernelModeOnly]
[-LogType <String>]
[-Deploy]
[-ExtremeVisibility]
[<CommonParameters>]
This is a multi-purpose cmdlet that offers a wide range of functionalities that can either be used separately or mixed together for very detailed and specific tasks.
It currently supports Code Integrity and AppLocker logs from the following sources:
- Local Event logs
- Evtx log files
- Microsoft Defender for Endpoint Advanced Hunting results
The cmdlet displays the logs in a GUI and allows the user to select the logs to be processed further.
The logs can be filtered based on many criteria using the available parameters.
The output of this cmdlet is a Supplemental Application Control (WDAC) policy. Based on the input parameters, it can be associated with a base policy or merged with an existing Base or Supplemental policy.
The cmdlet can be used for local and remote systems. You can utilize this cmdlet to create App Control for Business policies from MDE Advanced Hunting and then deploy them using Microsoft Intune to your endpoints.
You can utilize this cmdlet to use the evtx log files you aggregated from your endpoints and create an App Control policy from them.
This offers scalability and flexibility in managing your security policies.
The policy to add the selected logs to, it can either be a base or supplemental policy.
Important
Only select one of the following three parameters: -PolicyToAddLogsTo
, -BasePolicyFile
, or -BasePolicyGUID
.
Type: | FileInfo |
---|---|
Aliases: | AddLogs |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The base policy file to associate the supplemental policy with.
Important
Only select one of the following three parameters: -PolicyToAddLogsTo
, -BasePolicyFile
, or -BasePolicyGUID
.
Type: | FileInfo |
---|---|
Aliases: | BaseFile |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The GUID of the base policy to associate the supplemental policy with.
Important
Only select one of the following three parameters: -PolicyToAddLogsTo
, -BasePolicyFile
, or -BasePolicyGUID
.
Type: | Guid |
---|---|
Aliases: | BaseGUID |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The source of the logs. Supports validate set and auto-completion, press TAB key to view the list of the available options.
Type: | String |
---|---|
Aliases: | Src |
Position: | Named |
Accepted values: |
LocalEventLogs , MDEAdvancedHunting , EVTXFiles
|
Default value: | LocalEventLogs |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The name of the supplemental policy to create
Type: | String |
---|---|
Aliases: | Name |
Position: | Named |
Default value: | The cmdlet will generate a proper name based on the selected source and time |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The level determining rule generation can be one of the following: Auto, FilePublisher, Publisher, or Hash.
The fallback level is always Hash.
By default, which is the same as not using this parameter, the most secure levels are prioritized. If a log contains the requisite details for the FilePublisher level, it will be utilized. If not, the Publisher level will be attempted. Should this also fail, the Hash level will be employed.
Type: | String |
---|---|
Aliases: | Lvl |
Position: | Named |
Default value: | Auto |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The path(s) to use MDE AH CSV files.
Note
This is a dynamic parameter and will only be available if the Source parameter is set to MDEAdvancedHunting.
Important
Please read this article for complete information on how to use this feature.
Type: | FileInfo[] |
---|---|
Aliases: | MDELogs |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The path(s) of EVTX files to use.
Note
This is a dynamic parameter and will only be available if the Source parameter is set to EVTXFiles.
Type: | FileInfo[] |
---|---|
Aliases: | Evtx |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The unit of time to use when filtering the logs by the time.
Type: | String |
---|---|
Aliases: | Duration |
Position: | Named |
Accepted values: |
Minutes , Hours , Days
|
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The number of the selected time unit to go back in time from the current time.
Note
This is a dynamic parameter and will only be available if the TimeSpan parameter is set.
Type: | String |
---|---|
Aliases: | Past |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The names of the policies to filter the logs by. Supports auto-completion, press TAB key to view the list of the deployed base policy names to choose from. It will not display the policies that are already selected on the command line.
You can manually enter the name of the policies that are no longer available on the system.
Type: | String[] |
---|---|
Aliases: | FilterNames |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
If used, will filter the logs by including only the Kernel-Mode logs.
Type: | SwitchParameter |
---|---|
Aliases: | KMode |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
The type of logs to display.
Type: | String |
---|---|
Aliases: | LogKind |
Position: | Named |
Accepted values: |
Audit , Blocked
|
Default value: | Audit |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
If used, will deploy the policy on the system.
Type: | SwitchParameter |
---|---|
Aliases: | Up |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
If used, will display all the properties of the logs without any filtering.
Type: | SwitchParameter |
---|---|
Aliases: | XVis |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
- 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-SupplementalWDACConfig
- Remove-WDACConfig
- Edit-WDACConfig
- Edit-SignedWDACConfig
- Deploy-SignedWDACConfig
- Confirm-WDACConfig
- New-DenyWDACConfig
- Set-CommonWDACConfig
- New-KernelModeWDACConfig
- Get-CommonWDACConfig
- Remove-CommonWDACConfig
- Assert-WDACConfigIntegrity
- Build-WDACCertificate
- 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