mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge pull request #9452 from jgeurten/jgeurten-update-driver-blocks
Updating the recommended driver blocklists with the prerelease vulnerable driver blocks
This commit is contained in:
commit
cbef9809b0
File diff suppressed because it is too large
Load Diff
@ -3,7 +3,7 @@ title: Windows Defender Application Control Wizard WDAC Event Parsing
|
|||||||
description: Creating WDAC policy rules from the WDAC event logs and the MDE Advanced Hunting WDAC events.
|
description: Creating WDAC policy rules from the WDAC event logs and the MDE Advanced Hunting WDAC events.
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.topic: conceptual
|
ms.topic: conceptual
|
||||||
ms.date: 02/01/2023
|
ms.date: 01/24/2024
|
||||||
---
|
---
|
||||||
|
|
||||||
# Creating WDAC Policy Rules from WDAC Events in the Wizard
|
# Creating WDAC Policy Rules from WDAC Events in the Wizard
|
||||||
@ -21,11 +21,11 @@ As of [version 2.2.0.0](https://webapp-wdac-wizard.azurewebsites.net/archives.ht
|
|||||||
|
|
||||||
To create rules from the WDAC event logs on the system:
|
To create rules from the WDAC event logs on the system:
|
||||||
|
|
||||||
1. Select **Policy Editor** from the WDAC Wizard main page.
|
1. Select **Policy Editor** from the main page.
|
||||||
2. Select **Convert Event Log to a WDAC Policy**.
|
2. Select **Convert Event Log to a WDAC Policy**.
|
||||||
3. Select the **Parse Event Logs** button under the **Parse Event Logs from the System Event Viewer to Policy** header.
|
3. Select the **Parse Event Logs** button under the **Parse Event Logs from the System Event Viewer to Policy** header.
|
||||||
|
|
||||||
The Wizard will parse the relevant audit and block events from the CodeIntegrity (WDAC) Operational and AppLocker MSI and Script logs. You'll see a notification when the Wizard successfully finishes reading the events.
|
The Wizard parses the relevant audit and block events from the CodeIntegrity (WDAC) Operational and AppLocker MSI and Script logs. You see a notification when the Wizard successfully finishes reading the events.
|
||||||
|
|
||||||
> [!div class="mx-imgBorder"]
|
> [!div class="mx-imgBorder"]
|
||||||
> [](../images/wdac-wizard-event-log-system-expanded.png)
|
> [](../images/wdac-wizard-event-log-system-expanded.png)
|
||||||
@ -37,12 +37,12 @@ To create rules from the WDAC event logs on the system:
|
|||||||
|
|
||||||
To create rules from the WDAC `.EVTX` event logs files on the system:
|
To create rules from the WDAC `.EVTX` event logs files on the system:
|
||||||
|
|
||||||
1. Select **Policy Editor** from the WDAC Wizard main page.
|
1. Select **Policy Editor** from the main page.
|
||||||
2. Select **Convert Event Log to a WDAC Policy**.
|
2. Select **Convert Event Log to a WDAC Policy**.
|
||||||
3. Select the **Parse Log File(s)** button under the **Parse Event Log evtx Files to Policy** header.
|
3. Select the **Parse Log File(s)** button under the **Parse Event Log evtx Files to Policy** header.
|
||||||
4. Select the WDAC CodeIntegrity Event log EVTX file(s) from the disk to parse.
|
4. Select the WDAC CodeIntegrity Event log EVTX file(s) from the disk to parse.
|
||||||
|
|
||||||
The Wizard will parse the relevant audit and block events from the selected log files. You'll see a notification when the Wizard successfully finishes reading the events.
|
The Wizard parses the relevant audit and block events from the selected log files. You see a notification when the Wizard successfully finishes reading the events.
|
||||||
|
|
||||||
> [!div class="mx-imgBorder"]
|
> [!div class="mx-imgBorder"]
|
||||||
> [](../images/wdac-wizard-event-log-files-expanded.png)
|
> [](../images/wdac-wizard-event-log-files-expanded.png)
|
||||||
@ -57,7 +57,7 @@ To create rules from the WDAC events in [MDE Advanced Hunting](../operations/que
|
|||||||
1. Navigate to the Advanced Hunting section within the MDE console and query the WDAC events. **The Wizard requires the following fields** in the Advanced Hunting csv file export:
|
1. Navigate to the Advanced Hunting section within the MDE console and query the WDAC events. **The Wizard requires the following fields** in the Advanced Hunting csv file export:
|
||||||
|
|
||||||
```KQL
|
```KQL
|
||||||
| project Timestamp, DeviceId, DeviceName, ActionType, FileName, FolderPath, SHA1, SHA256, IssuerName, IssuerTBSHash, PublisherName, PublisherTBSHash, AuthenticodeHash, PolicyId, PolicyName
|
| project-keep Timestamp, DeviceId, DeviceName, ActionType, FileName, FolderPath, SHA1, SHA256, IssuerName, IssuerTBSHash, PublisherName, PublisherTBSHash, AuthenticodeHash, PolicyId, PolicyName
|
||||||
```
|
```
|
||||||
|
|
||||||
The following Advanced Hunting query is recommended:
|
The following Advanced Hunting query is recommended:
|
||||||
@ -76,7 +76,7 @@ To create rules from the WDAC events in [MDE Advanced Hunting](../operations/que
|
|||||||
| extend PolicyId = parsejson(AdditionalFields).PolicyID
|
| extend PolicyId = parsejson(AdditionalFields).PolicyID
|
||||||
| extend PolicyName = parsejson(AdditionalFields).PolicyName
|
| extend PolicyName = parsejson(AdditionalFields).PolicyName
|
||||||
// Keep only required fields for the WDAC Wizard
|
// Keep only required fields for the WDAC Wizard
|
||||||
| project Timestamp,DeviceId,DeviceName,ActionType,FileName,FolderPath,SHA1,SHA256,IssuerName,IssuerTBSHash,PublisherName,PublisherTBSHash,AuthenticodeHash,PolicyId,PolicyName
|
| project-keep Timestamp,DeviceId,DeviceName,ActionType,FileName,FolderPath,SHA1,SHA256,IssuerName,IssuerTBSHash,PublisherName,PublisherTBSHash,AuthenticodeHash,PolicyId,PolicyName
|
||||||
```
|
```
|
||||||
|
|
||||||
2. Export the WDAC event results by selecting the **Export** button in the results view.
|
2. Export the WDAC event results by selecting the **Export** button in the results view.
|
||||||
@ -84,12 +84,12 @@ To create rules from the WDAC events in [MDE Advanced Hunting](../operations/que
|
|||||||
> [!div class="mx-imgBorder"]
|
> [!div class="mx-imgBorder"]
|
||||||
> [](../images/wdac-wizard-event-log-mde-ah-export-expanded.png)
|
> [](../images/wdac-wizard-event-log-mde-ah-export-expanded.png)
|
||||||
|
|
||||||
3. Select **Policy Editor** from the WDAC Wizard main page.
|
3. Select **Policy Editor** from the main page.
|
||||||
4. Select **Convert Event Log to a WDAC Policy**.
|
4. Select **Convert Event Log to a WDAC Policy**.
|
||||||
5. Select the **Parse Log File(s)** button under the "Parse MDE Advanced Hunting Events to Policy" header.
|
5. Select the **Parse Log File(s)** button under the "Parse MDE Advanced Hunting Events to Policy" header.
|
||||||
6. Select the WDAC MDE Advanced Hunting export CSV files from the disk to parse.
|
6. Select the WDAC MDE Advanced Hunting export CSV files from the disk to parse.
|
||||||
|
|
||||||
The Wizard will parse the relevant audit and block events from the selected Advanced Hunting log files. You'll see a notification when the Wizard successfully finishes reading the events.
|
The Wizard will parse the relevant audit and block events from the selected Advanced Hunting log files. You see a notification when the Wizard successfully finishes reading the events.
|
||||||
|
|
||||||
> [!div class="mx-imgBorder"]
|
> [!div class="mx-imgBorder"]
|
||||||
> [](../images/wdac-wizard-event-log-mde-ah-parsing-expanded.png)
|
> [](../images/wdac-wizard-event-log-mde-ah-parsing-expanded.png)
|
||||||
@ -99,14 +99,14 @@ To create rules from the WDAC events in [MDE Advanced Hunting](../operations/que
|
|||||||
|
|
||||||
## Creating Policy Rules from the Events
|
## Creating Policy Rules from the Events
|
||||||
|
|
||||||
On the "Configure Event Log Rules" page, the unique WDAC log events will be shown in the table. Event Ids, filenames, product names, the policy name that audited or blocked the file, and the file publisher are all shown in the table. The table can be sorted alphabetically by clicking on any of the headers.
|
On the "Configure Event Log Rules" page, the unique WDAC log events are shown in the table. Event Ids, filenames, product names, the policy name that audited or blocked the file, and the file publisher are all shown in the table. The table can be sorted alphabetically by clicking on any of the headers.
|
||||||
|
|
||||||
To create a rule and add it to the WDAC policy:
|
To create a rule and add it to the WDAC policy:
|
||||||
|
|
||||||
1. Select an audit or block event in the table by selecting the row of interest.
|
1. Select an audit or block event in the table by selecting the row of interest.
|
||||||
2. Select a rule type from the dropdown. The Wizard supports creating Publisher, Path, File Attribute, Packaged App and Hash rules.
|
2. Select a rule type from the dropdown. The Wizard supports creating Publisher, Path, File Attribute, Packaged App and Hash rules.
|
||||||
3. Select the attributes and fields that should be added to the policy rules using the checkboxes provided for the rule type.
|
3. Select the attributes and fields that should be added to the policy rules using the checkboxes provided for the rule type.
|
||||||
4. Select the **Add Allow Rule** button to add the configured rule to the policy generated by the Wizard. The "Added to policy" label will be added to the selected row confirming that the rule will be generated.
|
4. Select the **Add Allow Rule** button to add the configured rule to the policy generated by the Wizard. The "Added to policy" label is shown in the selected row confirming that the rule will be generated.
|
||||||
|
|
||||||
> [!div class="mx-imgBorder"]
|
> [!div class="mx-imgBorder"]
|
||||||
> [](../images/wdac-wizard-event-rule-creation-expanded.png)
|
> [](../images/wdac-wizard-event-rule-creation-expanded.png)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user