You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/release-notes.md
+27-3Lines changed: 27 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,30 @@ For more information on what's new with other Microsoft Defender security produc
20
20
For news about earlier releases, see [Archive of past updates for Microsoft Defender for Cloud Apps](release-note-archive.md).
21
21
22
22
23
+
## October 2024
24
+
25
+
### New anomaly data in advanced hunting CloudAppEvents table
26
+
27
+
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal, can now utilize the new *LastSeenForUser* and *UncommonForUser* columns for queries and detections rules.
28
+
The new columns are designed to assist you to better __identify uncommon activities__ that may appear suspicious, and allow you to create more accurate custom detections, as well as investigate any suspicious activities that arise.
29
+
30
+
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
31
+
32
+
### New Conditional Access app control / inline data in advanced hunting CloudAppEvents table
33
+
34
+
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new *AuditSource* and *SessionData* columns for queries and detection rules.
35
+
Using this data allows for queries that consider specific audit sources, including access and session control, and queries by specific inline sessions.
36
+
37
+
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
38
+
39
+
### New data in advanced hunting CloudAppEvents table - OAuthAppId
40
+
41
+
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new _OAuthAppId_ column for queries and detection rules.
42
+
43
+
Using _OAuthAppId_ allows the queries that consider specific OAuth applications, making queries and detection rules more accurate.
44
+
45
+
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
46
+
23
47
## September 2024
24
48
25
49
### Enforce Edge in-browser when accessing business apps
@@ -28,7 +52,7 @@ Administrators who understand the power of Edge in-browser protection, can now r
28
52
A primary reason is security, since the barrier to circumventing session controls using Edge is much higher than with reverse proxy technology.
29
53
30
54
For more information see:
31
-
[Enforce Edge in-browser protection when accessing business apps](https://learn.microsoft.com/defender-cloud-apps/in-browser-protection#enforce-edge-in-browser-when-accessing-business-apps)
55
+
[Enforce Edge in-browser protection when accessing business apps](/defender-cloud-apps/in-browser-protection)
32
56
33
57
### Connect Mural to Defender for Cloud Apps (Preview)
34
58
@@ -146,7 +170,7 @@ Microsoft Defender for Cloud Apps log collector now supports [Azure Kubernetes S
146
170
147
171
For more information, see [Configure automatic log upload using Docker on Azure Kubernetes Service (AKS)](discovery-kubernetes.md).
148
172
149
-
### New Conditional Access app control / inline data for the advanced hunting CloudAppEvents table
173
+
### New Conditional Access app control / inline data for the advanced hunting CloudAppEvents table (Preview)
150
174
151
175
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new *AuditSource* and *SessionData* columns for queries and detection rules. Using this data allows for queries that consider specific audit sources, including access and session control, and queries by specific inline sessions.
152
176
@@ -224,7 +248,7 @@ Automatic log collection is supported using a Docker container on multiple opera
224
248
225
249
For more information, see [Configure automatic log upload using Podman](discovery-linux-podman.md).
226
250
227
-
### New anomaly data for the advanced hunting CloudAppEvents table
251
+
### New anomaly data for the advanced hunting CloudAppEvents table (Preview)
228
252
229
253
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new *LastSeenForUser* and *UncommonForUser* columns for queries and detections rules. Using this data helps to rule out false positives and find anomalies.
Copy file name to clipboardExpand all lines: defender-endpoint/comprehensive-guidance-on-linux-deployment.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: conceptual
15
15
ms.subservice: linux
16
16
search.appverid: met150
17
-
ms.date: 09/10/2024
17
+
ms.date: 10/28/2024
18
18
---
19
19
20
20
# Advanced deployment guidance for Microsoft Defender for Endpoint on Linux
@@ -167,8 +167,6 @@ For a detailed list of supported Linux distros, see [System requirements](micros
167
167
|OS version|Kernel filter driver|Comments|
168
168
|---|---|---|
169
169
|RHEL 7.x, RHEL 8.x, and RHEL 9.x |No kernel filter driver, the fanotify kernel option must be enabled|akin to Filter Manager (fltmgr, accessible via `fltmc.exe`) in Windows|
170
-
|RHEL 6.x|TALPA kernel driver|
171
-
172
170
## 7. Add your existing solution to the exclusion list for Microsoft Defender Antivirus
173
171
174
172
This step of the setup process involves adding Defender for Endpoint to the exclusion list for your existing endpoint protection solution and any other security products your organization is using. You can choose from several methods to add your exclusions to Microsoft Defender Antivirus.
Copy file name to clipboardExpand all lines: defender-endpoint/deployment-vdi-microsoft-defender-antivirus.md
+13-15Lines changed: 13 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Configure Microsoft Defender Antivirus on a remote desktop or virtual desktop infrastructure environment
3
3
description: Get an overview of how to configure Microsoft Defender Antivirus in a remote desktop or non-persistent virtual desktop environment.
4
4
ms.localizationpriority: medium
5
-
ms.date: 09/27/2024
5
+
ms.date: 10/28/2024
6
6
ms.topic: conceptual
7
7
author: denisebmsft
8
8
ms.author: deniseb
@@ -31,8 +31,7 @@ search.appverid: met150
31
31
32
32
- Windows
33
33
34
-
> [!TIP]
35
-
> This article is designed for customers who are using Microsoft Defender Antivirus capabilities only. If you have Microsoft Defender for Endpoint (which includes Microsoft Defender Antivirus alongside additional device protection capabilities), skip this article and proceed to [Onboard non-persistent virtual desktop infrastructure (VDI) devices in Microsoft Defender XDR](configure-endpoints-vdi.md).
34
+
This article is designed for customers who are using Microsoft Defender Antivirus capabilities only. If you have Microsoft Defender for Endpoint (which includes Microsoft Defender Antivirus alongside other device protection capabilities), also go through [Onboard non-persistent virtual desktop infrastructure (VDI) devices in Microsoft Defender XDR](configure-endpoints-vdi.md).
36
35
37
36
You can use Microsoft Defender Antivirus in a remote desktop (RDS) or non-persistent virtual desktop infrastructure (VDI) environment. Following the guidance in this article, you can configure updates to download directly to your RDS or VDI environments when a user signs in.
38
37
@@ -43,7 +42,7 @@ This guide describes how to configure Microsoft Defender Antivirus on your VMs f
43
42
-[Use quick scans](#use-quick-scans)
44
43
-[Prevent notifications](#prevent-notifications)
45
44
-[Disable scans from occurring after every update](#disable-scans-after-an-update)
46
-
-[Scan out-of-date machines or machines that have been offline for a while](#scan-vms-that-have-been-offline)
45
+
-[Scan out-of-date machines or machines that were offline for a while](#scan-vms-that-have-been-offline)
47
46
-[Apply exclusions](#exclusions)
48
47
49
48
> [!IMPORTANT]
@@ -67,7 +66,7 @@ In Windows 10, version 1903, Microsoft introduced the shared security intelligen
67
66
68
67
5. Enter `\\<Windows File Server shared location\>\wdav-update` (for help with this value, see [Download and unpackage](#download-and-unpackage-the-latest-updates)).
69
68
70
-
6. Select **OK**, and then deploy the GPO to the VMs you want to test.
69
+
6. Select **OK**, and then deploy the Group Policy Object to the VMs you want to test.
You can set a scheduled task to run once a day so that whenever the package is downloaded and unpacked then the VMs receive the new update. We suggest starting with once a day, but you should experiment with increasing or decreasing the frequency to understand the impact.
98
97
99
-
Security intelligence packages are typically published once every three to four hours. Setting a frequency shorter than four hours isn't advisable because it will increase the network overhead on your management machine for no benefit.
98
+
Security intelligence packages are typically published once every three to four hours. Setting a frequency shorter than four hours isn't advisable because it increases the network overhead on your management machine for no benefit.
100
99
101
-
You can also set up your single server or machine to fetch the updates on behalf of the VMs at an interval and place them in the file share for consumption.
102
-
This configuration is possible when the devices have the share and read access (NTFS permissions) to the share so they can grab the updates. To set up this configuration, follow these steps:
100
+
You can also set up your single server or machine to fetch the updates on behalf of the VMs at an interval and place them in the file share for consumption. This configuration is possible when the devices have share and read access (NTFS permissions) to the share so they can grab the updates. To set up this configuration, follow these steps:
103
101
104
102
1. Create an SMB/CIFS file share.
105
103
@@ -122,7 +120,7 @@ This configuration is possible when the devices have the share and read access (
122
120
123
121
### Set a scheduled task to run the PowerShell script
124
122
125
-
1. On the management machine, open the Start menu and type `Task Scheduler`. From the results, Task Scheduler and then select **Create task...**on the side panel.
123
+
1. On the management machine, open the Start menu and type `Task Scheduler`. From the results, select Task Scheduler and then select **Create task...**in the side panel.
126
124
127
125
2. Specify the name as `Security intelligence unpacker`.
128
126
@@ -151,7 +149,7 @@ If you would prefer to do everything manually, here's what to do to replicate th
151
149
Here's an example: `c:\wdav_update\{00000000-0000-0000-0000-000000000000}`
152
150
153
151
> [!NOTE]
154
-
> In the script we set it so the last 12 digits of the GUID are the year, month, day, and time when the file was downloaded so that a new folder is created each time. You can change this so that the file is downloaded to the same folder each time.
152
+
> We set the script so that the last 12 digits of the GUID are the year, month, day, and time when the file was downloaded so that a new folder is created each time. You can change this so that the file is downloaded to the same folder each time.
155
153
156
154
3. Download a security intelligence package from [https://www.microsoft.com/wdsi/definitions](https://www.microsoft.com/wdsi/definitions) into the GUID folder. The file should be named `mpam-fe.exe`.
157
155
@@ -164,7 +162,7 @@ If you would prefer to do everything manually, here's what to do to replicate th
164
162
165
163
Scheduled scans run in addition to [real-time protection and scanning](configure-real-time-protection-microsoft-defender-antivirus.md).
166
164
167
-
The start time of the scan itself is still based on the scheduled scan policy (**ScheduleDay**, **ScheduleTime**, and **ScheduleQuickScanTime**). Randomization will cause Microsoft Defender Antivirus to start a scan on each machine within a four-hour window from the time set for the scheduled scan.
165
+
The start time of the scan itself is still based on the scheduled scan policy (**ScheduleDay**, **ScheduleTime**, and **ScheduleQuickScanTime**). Randomization causes Microsoft Defender Antivirus to start a scan on each machine within a four-hour window from the time set for the scheduled scan.
168
166
169
167
See [Schedule scans](schedule-antivirus-scans.md) for other configuration options available for scheduled scans.
170
168
@@ -194,14 +192,14 @@ Sometimes, Microsoft Defender Antivirus notifications are sent to or persist acr
194
192
195
193
4. Deploy your Group Policy object as you usually do.
196
194
197
-
Suppressing notifications prevents notifications from Microsoft Defender Antivirus from showing up when scans are done or remediation actions are taken. However, your security operations team will see the results of a scan if an attack is detected and stopped. Alerts, such as an initial access alert, are generated and will appear in the [Microsoft Defender portal](https://security.microsoft.com).
195
+
Suppressing notifications prevents notifications from Microsoft Defender Antivirus from showing up when scans are done or remediation actions are taken. However, your security operations team sees the results of a scan if an attack is detected and stopped. Alerts, such as an initial access alert, are generated, and appear in the [Microsoft Defender portal](https://security.microsoft.com).
198
196
199
197
## Disable scans after an update
200
198
201
-
Disabling a scan after an update will prevent a scan from occurring after receiving an update. You can apply this setting when creating the base image if you have also run a quick scan. This way, you can prevent the newly updated VM from performing a scan again (as you've already scanned it when you created the base image).
199
+
Disabling a scan after an update prevents a scan from occurring after receiving an update. You can apply this setting when creating the base image if you have also run a quick scan. This way, you can prevent the newly updated VM from performing a scan again (as you've already scanned it when you created the base image).
202
200
203
201
> [!IMPORTANT]
204
-
> Running scans after an update will help ensure your VMs are protected with the latest security intelligence updates. Disabling this option will reduce the protection level of your VMs and should only be used when first creating or deploying the base image.
202
+
> Running scans after an update helps ensure your VMs are protected with the latest security intelligence updates. Disabling this option reduces the protection level of your VMs and should only be used when first creating or deploying the base image.
205
203
206
204
1. In your Group Policy Editor, go to **Windows components**\>**Microsoft Defender Antivirus**\>**Security Intelligence Updates**.
207
205
@@ -239,7 +237,7 @@ For more information, see [Start the scheduled scan only when computer is on but
239
237
240
238
5. Deploy your Group Policy Object as you usually do.
241
239
242
-
This policy forces a scan if the VM has missed two or more consecutive scheduled scans.
240
+
This policy forces a scan if the VM missed two or more consecutive scheduled scans.
0 commit comments