Skip to content

Commit c57f0f7

Browse files
authored
Merge branch 'main' into protect-ot-article-in-xdr
2 parents 709eb1d + d03ccb2 commit c57f0f7

File tree

543 files changed

+3396
-1761
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

543 files changed

+3396
-1761
lines changed

.openpublishing.redirection.defender-xdr.json

Lines changed: 81 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@
1010
"redirect_url": "/defender-for-identity/microsoft-365-security-center-mdi",
1111
"redirect_document_id": false
1212
},
13-
1413
{
1514
"source_path": "defender-xdr/eval-create-eval-environment.md",
1615
"redirect_url": "/defender-xdr/pilot-deploy-overview",
@@ -171,6 +170,31 @@
171170
"redirect_url": "/defender-xdr/",
172171
"redirect_document_id": false
173172
},
173+
{
174+
"source_path": "defender-xdr/microsoft-threat-actor-naming.md",
175+
"redirect_url": "/unified-secops-platform/microsoft-threat-actor-naming",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path": "defender-xdr/malware-naming.md",
180+
"redirect_url": "/unified-secops-platform/malware-naming",
181+
"redirect_document_id": false
182+
},
183+
{
184+
"source_path": "defender-xdr/criteria.md",
185+
"redirect_url": "/unified-secops-platform/criteria",
186+
"redirect_document_id": false
187+
},
188+
{
189+
"source_path": "defender-xdr/submission-guide.md",
190+
"redirect_url": "/unified-secops-platform/submission-guide",
191+
"redirect_document_id": false
192+
},
193+
{
194+
"source_path": "defender-xdr/virus-initiative-criteria.md",
195+
"redirect_url": "/unified-secops-platform/virus-initiative-criteria",
196+
"redirect_document_id": false
197+
},
174198
{
175199
"source_path": "defender-xdr/tickets.md",
176200
"redirect_url": "/defender-xdr/troubleshoot",
@@ -180,6 +204,61 @@
180204
"source_path": "defender-xdr/portal-submission-troubleshooting.md",
181205
"redirect_url": "/defender-xdr/troubleshoot",
182206
"redirect_document_id": false
207+
},
208+
{
209+
"source_path": "defender-xdr/mto-advanced-hunting.md",
210+
"redirect_url": "/unified-secops-platform/mto-advanced-hunting",
211+
"redirect_document_id": false
212+
},
213+
{
214+
"source_path": "defender-xdr/mto-dashboard.md",
215+
"redirect_url": "/unified-secops-platform/mto-dashboard",
216+
"redirect_document_id": false
217+
},
218+
{
219+
"source_path": "defender-xdr/mto-endpoint-security-policy.md",
220+
"redirect_url": "/unified-secops-platform/mto-endpoint-security-policy",
221+
"redirect_document_id": false
222+
},
223+
{
224+
"source_path": "defender-xdr/mto-incidents-alerts.md",
225+
"redirect_url": "/unified-secops-platform/mto-incidents-alerts",
226+
"redirect_document_id": false
227+
},
228+
{
229+
"source_path": "defender-xdr/mto-overview.md",
230+
"redirect_url": "/unified-secops-platform/mto-overview",
231+
"redirect_document_id": false
232+
},
233+
{
234+
"source_path": "defender-xdr/mto-requirements.md",
235+
"redirect_url": "/unified-secops-platform/mto-requirements",
236+
"redirect_document_id": false
237+
},
238+
{
239+
"source_path": "defender-xdr/mto-tenant-devices.md",
240+
"redirect_url": "/unified-secops-platform/mto-tenant-devices",
241+
"redirect_document_id": false
242+
},
243+
{
244+
"source_path": "defender-xdr/mto-tenantgroups.md",
245+
"redirect_url": "/unified-secops-platform/mto-tenantgroups",
246+
"redirect_document_id": false
247+
},
248+
{
249+
"source_path": "defender-xdr/mto-tenants.md",
250+
"redirect_url": "/unified-secops-platform/mto-tenants",
251+
"redirect_document_id": false
252+
},
253+
{
254+
"source_path": "defender-xdr/portals.md",
255+
"redirect_url": "/unified-secops-platform/overview-plan#understand-microsoft-security-portals-and-admin-centers",
256+
"redirect_document_id": false
257+
},
258+
{
259+
"source_path": "defender-xdr/microsoft-sentinel-onboard.md",
260+
"redirect_url": "/unified-secops-platform/microsoft-sentinel-onboard",
261+
"redirect_document_id": false
183262
}
184263
]
185-
}
264+
}
-43.2 KB
Binary file not shown.

ATPDocs/deploy/active-directory-federation-services.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,6 @@ Configure the SQL server to allow the Directory Service Account with the followi
5555
- *read*
5656
- *select*
5757

58-
> [!NOTE]
59-
> If the AD FS database runs on a dedicated SQL server instead of the local AD FS server, and you're using a group Managed Service Account (gMSA) as the Directory Service Account, make sure that you grant the SQL server the [required permissions](create-directory-service-account-gmsa.md#prerequisites-grant-permissions-to-retrieve-the-gmsa-accounts-password) to retrieve the gMSA's password.
60-
6158
### Grant access to the AD FS database
6259

6360
Grant access to the AD FS database by using SQL Server Management Studio, Transact-SQL (T-SQL), or PowerShell.

ATPDocs/deploy/deploy-defender-identity.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,8 @@ Use the following steps to prepare for deploying Defender for Identity:
5050
1. [Plan your Defender for Identity capacity](capacity-planning.md).
5151

5252
> [!TIP]
53-
> We recommend running the [*Test-MdiReadiness.ps1*](https://github.com/microsoft/Microsoft-Defender-for-Identity/tree/main/Test-MdiReadiness) script to test and see if your environment has the necessary prerequisites.
54-
>
55-
> The link to the *Test-MdiReadiness.ps1* script is also available from Microsoft Defender XDR, on the **Identities > Tools** page (Preview).
53+
> We recommend running the [*Test-MdiReadiness.ps1*](https://github.com/microsoft/Microsoft-Defender-for-Identity/tree/main/Test-MdiReadiness) script to test and see if the servers in your environment have the necessary prerequisites.
54+
> You can use the [DefenderForIdentity PowerShell module](https://www.powershellgallery.com/packages/DefenderForIdentity/) to add the required auditing and configure the necessary settings.
5655
5756
## Deploy Defender for Identity
5857

@@ -71,12 +70,12 @@ The following procedures help you complete the deployment process:
7170

7271
- [**Enable and configure unified role-based access control (RBAC)**](../role-groups.md) for Defender for Identity.
7372

74-
- [**Configure a Directory Service account (DSA) for use with Defender for Identity**](directory-service-accounts.md). While a DSA is optional in some scenarios, we recommend that you configure a DSA for Defender for Identity for full security coverage. For example, when you have a DSA configured, the DSA is used to connect to the domain controller at startup. A DSA can also be used to query the domain controller for data on entities seen in network traffic, monitored events, and monitored ETW activities
73+
- [**Configure a Directory Service account (DSA) for use with Defender for Identity**](directory-service-accounts.md). While a DSA is optional in some scenarios, we recommend that you configure a DSA for Defender for Identity for full security coverage. For example, when you have a DSA configured, the DSA is used to connect to the domain controller at startup. A DSA can also be used to query the domain controller for data on entities seen in network traffic, monitored events, and monitored ETW activities.
7574

7675
- [**Configure remote calls to SAM**](remote-calls-sam.md) as needed. While this step is optional, we recommend that you configure remote calls to SAM-R for lateral movement path detection with Defender for Identity.
7776

7877
> [!TIP]
79-
> By default, Defender for Identity sensors query the directory using LDAP on ports 389 and 3268. To switch to LDAPS on ports 636 and 3269, please open a support case. For more information, see [Microsoft Defender for Identity support](../support.md).
78+
> By default, Defender for Identity sensors query the directory using LDAP on ports 389 and 3268. To switch to LDAPS on ports 636 and 3269, open a support case. For more information, see [Microsoft Defender for Identity support](../support.md).
8079
>
8180
8281
> [!IMPORTANT]

ATPDocs/privacy-compliance.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,14 @@ For more information see: [Microsoft Defender for Identity monitored activities]
2222

2323
Defender for Identity operates in the Microsoft Azure data centers in the following locations:
2424

25-
- European Union (West Europe, North Europe)
26-
- United Kingdom (UK South)
27-
- United States (East US, West US, West US2)
28-
- Australia (Australia East)
29-
- Switzerland (Switzerland North)
30-
- Singapore (Southeast Asia)
25+
- Asia (Southeast Asia)
26+
- Australia (Australia East, Australia Southeast)
27+
- Europe (West Europe, North Europe)
3128
- India (Central India, South India)
29+
- North America (East US, West US, West US2)
30+
- Switzerland (Switzerland North, Switzerland West)
31+
- United Kingdom (UK South)
32+
3233

3334
Customer data collected by the service might be stored as follows:
3435

CloudAppSecurityDocs/ops-guide/ops-guide-daily.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ Based on the data you review, you might want to create new or adjust app governa
146146

147147
For more information, see:
148148

149-
- [View and manage incidents and alerts](/microsoft-365/security/defender/mto-incidents-alerts)
149+
- [View and manage incidents and alerts](/unified-secops-platform/mto-incidents-alerts)
150150
- [View your app details with app governance](../app-governance-visibility-insights-view-apps.md)
151151
- [Create app policies in app governance](../app-governance-app-policies-create.md).
152152

@@ -163,7 +163,7 @@ App governance uses machine learning-based detection algorithms to detect anomal
163163

164164
For more information, see:
165165

166-
- [View and manage incidents and alerts](/microsoft-365/security/defender/mto-incidents-alerts)
166+
- [View and manage incidents and alerts](/unified-secops-platform/mto-incidents-alerts)
167167
- [View your app details with app governance](../app-governance-visibility-insights-view-apps.md)
168168
- [Getting detailed information on an app](../app-governance-visibility-insights-view-apps.md#getting-detailed-information-on-an-app)
169169

@@ -199,7 +199,7 @@ By default, there's no access or session policies deployed, and therefore no rel
199199

200200
For more information, see:
201201

202-
- [View and manage incidents and alerts](/microsoft-365/security/defender/mto-incidents-alerts)
202+
- [View and manage incidents and alerts](/unified-secops-platform/mto-incidents-alerts)
203203
- [Protect apps with Microsoft Defender for Cloud Apps Conditional Access app control](../proxy-intro-aad.md)
204204
- [Block and protect download of sensitive data to unmanaged or risky devices](../best-practices.md#block-and-protect-download-of-sensitive-data-to-unmanaged-or-risky-devices)
205205
- [Secure collaboration with external users by enforcing real-time session controls](../best-practices.md#secure-collaboration-with-external-users-by-enforcing-real-time-session-controls)
@@ -231,7 +231,7 @@ Create app discovery policies to start alerting and tagging newly discovered app
231231
232232
For more information, see:
233233

234-
- [View and manage incidents and alerts](/microsoft-365/security/defender/mto-incidents-alerts)
234+
- [View and manage incidents and alerts](/unified-secops-platform/mto-incidents-alerts)
235235
- [Cloud discovery policies](../policies-cloud-discovery.md)
236236
- [Create cloud discovery policies](../cloud-discovery-policies.md)
237237
- [Set up cloud discovery](../set-up-cloud-discovery.md)
@@ -298,7 +298,7 @@ Use the results of these queries to adjust existing file policies or create new
298298

299299
For more information, see:
300300

301-
- [View and manage incidents and alerts](/microsoft-365/security/defender/mto-incidents-alerts)
301+
- [View and manage incidents and alerts](/unified-secops-platform/mto-incidents-alerts)
302302
- [Information protection policies](../policies-information-protection.md).
303303

304304
## Related content

CloudAppSecurityDocs/protect-docusign.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,8 @@ ms.topic: how-to
77

88
# How Defender for Cloud Apps helps protect your DocuSign environment
99

10-
10+
> [!NOTE]
11+
> The DocuSign App Connector requires an active, paid DocuSign and DocuSign Monitor subscription to access and retrieve events.
1112
1213
DocuSign helps organizations manage electronic agreements, and so your DocuSign environment holds sensitive information for your organization. Any abuse of DocuSign by a malicious actor or any human error may expose your most critical assets to potential attacks.
1314

@@ -136,4 +137,4 @@ This section provides instructions for connecting Microsoft Defender for Cloud A
136137
> [!div class="nextstepaction"]
137138
> [Control cloud apps by using policies](control-cloud-apps-with-policies.md)
138139
139-
[!INCLUDE [Open support ticket](includes/support.md)]
140+
[!INCLUDE [Open support ticket](includes/support.md)]

CloudAppSecurityDocs/release-notes.md

Lines changed: 37 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,39 @@ For more information on what's new with other Microsoft Defender security produc
1919

2020
For news about earlier releases, see [Archive of past updates for Microsoft Defender for Cloud Apps](release-note-archive.md).
2121

22+
## February 2025
23+
24+
Due to improvements being made to Microsoft Defender for Cloud Apps to improve security and performance, you must update network information in your system's firewall and additional third-party services. Make these changes by March 16, 2025 to ensure uninterrupted access to our services:
25+
26+
- Update your firewall rules to allow outbound traffic on port 443 to the following new CDN (Content Delivery Network) endpoints before March 16, 2025:
27+
28+
- cdn.cloudappsecurity.com
29+
- cdn-discovery.cloudappsecurity.com
30+
31+
- All required outbound access URLs can also be found in Defender for Cloud Apps network requirements page under 'Portal Access'.
32+
33+
- To use Defender for Cloud Apps in the Microsoft Defender portal, make sure you add outbound port 443 for all IP addresses and DNS names listed in our documentation to your firewall's allowlist.
34+
35+
- To connect to third-party apps, enable Defender for Cloud Apps to connect from the following IP addresses, also available in our documentation:
36+
37+
- **US1**: - 23.101.201.123 - 20.228.186.154
38+
39+
- **US2**: - 20.15.114.156 - 172.202.90.196
40+
41+
- **US3**: - 20.3.226.231 - 4.255.218.227
42+
43+
- **EU1**: - 20.71.203.39 - 137.116.224.49
44+
45+
- **EU2**: - 20.0.210.84 - 20.90.9.64
46+
47+
- To stay up to date on IP ranges that impact the experiences in Microsoft Defender for Cloud Apps in the areas of portal experience access, access and session controls, SIEM agent connection, app connectors, mail servers, and log collector, we recommend using the Azure service tag for Microsoft Defender for Cloud Apps services, and 'MicrosoftCloudAppSecurity.' The latest IP ranges are found in the service tag. For more information, see [Azure IP ranges](/azure/virtual-network/service-tags-overview).
48+
2249
## November 2024
2350

2451
### Internal Session Controls application notice
25-
The Enterprise application “Microsoft Defender for Cloud Apps – Session Controls” is used internally by the Conditional Access App Control service.
26-
Please ensure there is no CA policy restricting access to this application.
52+
53+
The Enterprise application 'Microsoft Defender for Cloud Apps – Session Controls' is used internally by the Conditional Access App Control service.
54+
Ensure there's no CA policy restricting access to this application.
2755
For policies that restrict all or certain applications, please ensure this application is listed as an exception or confirm that the blocking policy is deliberate.
2856

2957
For more information, see [Sample: Create Microsoft Entra ID Conditional Access policies for use with Defender for Cloud Apps](session-policy-aad.md#sample-create-microsoft-entra-id-conditional-access-policies-for-use-with-defender-for-cloud-apps).
@@ -73,13 +101,13 @@ For more information, see [OAuth app data usage insights on app governance](/def
73101
### New anomaly data in advanced hunting CloudAppEvents table
74102

75103
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.
76-
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.
104+
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.
77105

78106
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
79107

80108
### New Conditional Access app control / inline data in advanced hunting CloudAppEvents table
81109

82-
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.
110+
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.
83111
Using this data allows for queries that consider specific audit sources, including access and session control, and queries by specific inline sessions.
84112

85113
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
@@ -100,8 +128,7 @@ Administrators who understand the power of Edge in-browser protection, can now r
100128

101129
A primary reason is security, since the barrier to circumventing session controls using Edge is much higher than with reverse proxy technology.
102130

103-
For more information see:
104-
[Enforce Edge in-browser protection when accessing business apps](in-browser-protection.md#enforce-microsoft-edge-browser-protection-when-accessing-business-apps)
131+
For more information see [Enforce Edge in-browser protection when accessing business apps](in-browser-protection.md#enforce-microsoft-edge-browser-protection-when-accessing-business-apps).
105132

106133
### Connect Mural to Defender for Cloud Apps (Preview)
107134

@@ -140,7 +167,7 @@ Use the feedback mechanisms at the top and bottom of each documentation page to
140167

141168
### Large scale export of Activity logs (Preview)
142169

143-
A new user experience dedicated to providing users the option to export from activity log page up to six months back or up to 100K events.
170+
A new user experience dedicated to providing users the option to export from 'activity log' page up to six months back or up to 100K events.
144171

145172
You can filter the results using time range and various other filters and even hide private activities.
146173

@@ -151,11 +178,12 @@ For more information, see [Export activities six months back](activity-filters-q
151178

152179
Customize the Microsoft Defender for Cloud Apps(MDA) block experience for apps that are blocked using Cloud Discovery.
153180

154-
You can set up a custom redirect URL on block pages
181+
You can set up a custom redirect URL on block pages:
182+
155183
- To educate and redirect end users to organization acceptable use policy
156184
- To guide end users on steps to follow to secure an exception for block
157185

158-
For more information, see [Configure custom URL for MDA block pages](mde-govern.md#educate-users-when-accessing-blocked-apps--customize-the-block-page)
186+
For more information, see [Configure custom URL for MDA block pages](mde-govern.md#educate-users-when-accessing-blocked-apps--customize-the-block-page).
159187

160188

161189
### In-browser protection for macOS users and newly supported policies (Preview)

0 commit comments

Comments
 (0)