Skip to content

Commit 1858542

Browse files
authored
Merge branch 'main' into mde-ios-updates
2 parents 8e35dd0 + a3b4d93 commit 1858542

File tree

1 file changed

+20
-46
lines changed

1 file changed

+20
-46
lines changed

defender-endpoint/enable-controlled-folders.md

Lines changed: 20 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ ms.service: defender-endpoint
55
ms.topic: conceptual
66
ms.localizationpriority: medium
77
audience: ITPro
8-
author: denisebmsft
9-
ms.author: deniseb
8+
author: emmwalshh
9+
ms.author: ewalsh
1010
ms.reviewer: sugamar; moeghasemi
1111
manager: deniseb
1212
ms.subservice: asr
@@ -15,7 +15,7 @@ ms.collection:
1515
- tier3
1616
- mde-asr
1717
search.appverid: met150
18-
ms.date: 07/25/2024
18+
ms.date: 03/12/2025
1919
---
2020

2121
# Enable controlled folder access
@@ -37,49 +37,21 @@ ms.date: 07/25/2024
3737

3838
You can enable controlled folder access by using any of these methods:
3939

40-
- [Windows Security app *](#windows-security-app)
41-
- [Microsoft Intune](#microsoft-intune)
42-
- [Mobile Device Management (MDM)](#mobile-device-management-mdm)
43-
- [Microsoft Configuration Manager](#microsoft-configuration-manager)
44-
- [Group Policy](#group-policy)
45-
- [PowerShell](#powershell)
46-
47-
> [!TIP]
48-
> Try using [audit mode](evaluate-controlled-folder-access.md) at first so you can see how the feature works and review events without impacting normal device usage in your organization.
49-
50-
> [!NOTE]
51-
> If you add Microsoft Defender Antivirus exclusions (process or path) for the binary in question, controlled folder access trusts it, and doesn't block the process or path. Group Policy settings that disable local administrator list merging override controlled folder access settings. They also override protected folders and allowed apps set by the local administrator through controlled folder access. These policies include:
52-
> - Microsoft Defender Antivirus **Configure local administrator merge behavior for lists**
53-
> - System Center Endpoint Protection **Allow users to add exclusions and overrides**
54-
55-
For more information about disabling local list merging, see [Prevent or allow users to locally modify Microsoft Defender Antivirus policy settings](/windows/security/threat-protection/microsoft-defender-antivirus/configure-local-policy-overrides-microsoft-defender-antivirus).
56-
57-
## Windows Security app
58-
59-
1. Open the Windows Security app by selecting the shield icon in the task bar. You can also search the start menu for **Windows Security**.
60-
61-
2. Select the **Virus & threat protection** tile (or the shield icon on the left menu bar) and then select **Ransomware protection**.
62-
63-
3. Set the switch for **Controlled folder access** to **On**.
64-
65-
> [!NOTE]
66-
> - This method is not available on Windows Server 2012 R2 or Windows Server 2016. If controlled folder access is configured with Group Policy, PowerShell, or MDM CSPs, the state changes in the Windows Security app only after restarting the device. If the feature is set to **Audit mode** with any of those tools, the Windows Security app shows the state as **Off**.
67-
>
68-
> - If you are protecting user profile data, the user profile should be on the default Windows installation drive.
69-
70-
## Microsoft Intune
71-
72-
1. Sign in to the [Microsoft Intune admin center](https://intune.microsoft.com) and open **Endpoint Security**.
73-
74-
2. Go to **Attack Surface Reduction** > **Policy**.
40+
- [Enable controlled folder access](#enable-controlled-folder-access)
41+
- [Enable controlled folder access](#enable-controlled-folder-access)
42+
- [Mobile Device Management (MDM)](#mobile-device-management-mdm)
43+
- [Microsoft Configuration Manager](#microsoft-configuration-manager)
44+
- [Group Policy](#group-policy)
45+
- [PowerShell](#powershell)
46+
- [See also](#see-also)
7547

7648
3. Select **Platform**, choose **Windows 10, Windows 11, and Windows Server**, and select the profile **Attack Surface Reduction rules** > **Create**.
7749

7850
4. Name the policy and add a description. Select **Next**.
7951

8052
5. Scroll down, and in the **Enable Controlled Folder Access** drop-down, select an option, such as **Audit Mode**.
8153

82-
We recommend enabling controlled folder access in audit mode first to see how it'll work in your organization. You can set it to another mode, such as **Enabled**, later.
54+
We recommend enabling controlled folder access in audit mode first to see how it works in your organization. You can set it to another mode, such as **Enabled**, later.
8355

8456
6. To optionally add folders that should be protected, select **Controlled Folder Access Protected Folders** and then add folders. Files in these folders can't be modified or deleted by untrusted applications. Keep in mind that your default system folders are automatically protected. You can view the list of default system folders in the Windows Security app on a Windows device. To learn more about this setting, see [Policy CSP - Defender: ControlledFolderAccessProtectedFolders](/windows/client-management/mdm/policy-csp-defender?#controlledfolderaccessprotectedfolders).
8557

@@ -90,7 +62,7 @@ For more information about disabling local list merging, see [Prevent or allow u
9062
9. Select **Next** to save each open blade and then **Create**.
9163

9264
> [!NOTE]
93-
> Wildcards are supported for applications, but not for folders. Allowed apps continue to trigger events until they are restarted.
65+
> Wildcards are supported for applications, but not for folders. Allowed apps continue to trigger events until they're restarted.
9466
9567
## Mobile Device Management (MDM)
9668

@@ -107,25 +79,27 @@ Use the [./Vendor/MSFT/Policy/Config/ControlledFolderAccessProtectedFolders](/wi
10779
1. Choose whether block or audit changes, allow other apps, or add other folders, and select **Next**.
10880

10981
> [!NOTE]
110-
> Wildcard is supported for applications, but not for folders. Allowed apps will continue to trigger events until they are restarted.
111-
82+
> Wildcard is supported for applications, but not for folders. Allowed apps continue to trigger events until they're restarted.
83+
11284
1. Review the settings and select **Next** to create the policy.
11385

114-
6. After the policy is created, **Close**.
86+
1. After the policy is created, **Close**.
87+
88+
For more information about Microsoft Configuration Manager and Controlled Folder Access, please visit [Controlled folder access policies and options](/mem/configmgr/protect/deploy-use/create-deploy-exploit-guard-policy).
11589

11690
## Group Policy
11791

118-
1. On your Group Policy management device, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and select **Edit**.
92+
1. On your Group Policy management device, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx). Right-click the Group Policy Object you want to configure and select **Edit**.
11993

12094
1. In the **Group Policy Management Editor**, go to **Computer configuration** and select **Administrative templates**.
12195

12296
1. Expand the tree to **Windows components > Microsoft Defender Antivirus > Microsoft Defender Exploit Guard > Controlled folder access**.
12397

12498
1. Double-click the **Configure Controlled folder access** setting and set the option to **Enabled**. In the options section you must specify one of the following options:
12599

126-
- **Enable** - Malicious and suspicious apps won't be allowed to make changes to files in protected folders. A notification will be provided in the Windows event log.
100+
- **Enable** - Malicious and suspicious apps aren't allowed to make changes to files in protected folders. A notification is provided in the Windows event log.
127101
- **Disable (Default)** - The Controlled folder access feature won't work. All apps can make changes to files in protected folders.
128-
- **Audit Mode** - Changes will be allowed if a malicious or suspicious app attempts to make a change to a file in a protected folder. However, it will be recorded in the Windows event log where you can assess the impact on your organization.
102+
- **Audit Mode** - Changes are allowed if a malicious or suspicious app attempts to make a change to a file in a protected folder. However, it's recorded in the Windows event log where you can assess the impact on your organization.
129103
- **Block disk modification only** - Attempts by untrusted apps to write to disk sectors will be logged in Windows Event log. These logs can be found in **Applications and Services Logs** > Microsoft > Windows > Windows Defender > Operational > ID 1123.
130104
- **Audit disk modification only** - Only attempts to write to protected disk sectors will be recorded in the Windows event log (under **Applications and Services Logs** > **Microsoft** > **Windows** > **Windows Defender** > **Operational** > **ID 1124**). Attempts to modify or delete files in protected folders won't be recorded.
131105

0 commit comments

Comments
 (0)