Skip to content

Commit 2c9d129

Browse files
committed
Merge branch 'main' into chrisda
2 parents 5b35187 + 57143e9 commit 2c9d129

31 files changed

+418
-214
lines changed

.openpublishing.redirection.defender-xdr.json

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "defender-xdr/microsoft-365-security-center-defender-cloud-apps.md",
5+
"redirect_url": "/defender-cloud-apps/microsoft-365-security-center-defender-cloud-apps",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "defender-xdr/microsoft-365-security-center-mdi.md",
10+
"redirect_url": "/defender-for-identity/microsoft-365-security-center-mdi",
11+
"redirect_document_id": false
12+
},
13+
314
{
415
"source_path": "defender-xdr/eval-create-eval-environment.md",
516
"redirect_url": "/defender-xdr/pilot-deploy-overview",

defender-xdr/microsoft-365-security-center-mdi.md renamed to ATPDocs/microsoft-365-security-center-mdi.md

Lines changed: 23 additions & 25 deletions
Large diffs are not rendered by default.

ATPDocs/toc.yml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,18 @@ items:
1111
href: zero-trust.md
1212
- name: System architecture
1313
href: architecture.md
14-
- name: Defender for Identity in Microsoft Defender XDR
15-
href: /microsoft-365/security/defender/microsoft-365-security-center-mdi?bc=/defender-for-identity/bread/toc.json&toc=/defender-for-identity/TOC.json
14+
- name: Defender for Identity in the Microsoft Defender portal
15+
href: microsoft-365-security-center-mdi.md
1616
- name: Defender for Identity for US Government
1717
href: us-govt-gcc-high.md
1818
- name: Deploy
1919
expanded: true
2020
items:
2121
- name: Quick installation guide
2222
href: deploy/quick-installation-guide.md
23-
- name: Deployment overview
23+
- name: Pilot and deploy Microsoft Defender XDR
24+
href: /defender-xdr/pilot-deploy-overview?toc=/defender-for-identity/toc.json&bc=/defender-for-identity/breadcrumb/toc.json
25+
- name: Defender for Identity deployment overview
2426
href: deploy/deploy-defender-identity.md
2527
- name: Plan and prepare
2628
items:

CloudAppSecurityDocs/investigate-anomaly-alerts.md

Lines changed: 4 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,6 @@ Following proper investigation, all Defender for Cloud Apps alerts can be classi
4040

4141
You should use the following general guidelines when investigating any type of alert to gain a clearer understanding of the potential threat before applying the recommended action.
4242

43-
- Review the user's [investigation priority score](tutorial-ueba.md#understand-the-investigation-priority-score) and compare with the rest of the organization. This will help you identify which users in your organization pose the greatest risk.
4443
- If you identify a **TP**, review all the user's activities to gain an understanding of the impact.
4544
- Review all user activity for other indicators of compromise and explore the source and scope of impact. For example, review the following user device information and compare with known device information:
4645
- Operating system and version
@@ -712,74 +711,14 @@ Establishing a new user's activity pattern requires an initial learning period o
712711
1. Review the deletion activities and create a list of deleted files. If needed, recover the deleted files.
713712
1. Optionally, create a playbook using Power Automate to contact users and their managers to verify the activity.
714713

715-
### Investigation priority score increase (preview)
714+
### Investigation priority score increase (legacy)
716715

717-
Anomalous activities and activities that triggered alerts are given scores based on severity, user impact, and behavioral analysis of the user. The analysis is done based on other users in the tenants.
716+
Starting November 2024, **Investigate risky users** support for Microsoft Defender for Cloud Apps is retired. If this feature was used in your organization and is needed, we recommend using the Entra risk score feature. Please use the following resources for additional information:
718717

719-
When there's a significant and anomalous increase in the investigation priority score of a certain user, the alert will be triggered.
718+
- [Investigate risk Microsoft Entra ID Protection - Microsoft Entra ID Protection | Microsoft Learn](/entra/id-protection/howto-identity-protection-investigate-risk)
720719

721-
This alert enables detecting potential breaches that are characterized by activities that don't necessarily trigger specific alerts but accumulate to a suspicious behavior for the user.
720+
- [Microsoft Entra ID Protection risk-based access policies - Microsoft Entra ID Protection | Microsoft Learn](/entra/id-protection/concept-identity-protection-policies)
722721

723-
**Learning period**
724-
725-
Establishing a new user's activity pattern requires an initial learning period of seven days, during which alerts aren't triggered for any score increase.
726-
727-
**TP**, **B-TP**, or **FP**?
728-
729-
1. **TP**: If you're able to confirm that the activities of the user aren't legitimate.
730-
731-
**Recommended action**: Suspend the user, mark the user as compromised, and reset their password.
732-
733-
1. **B-TP**: If you're able to confirm that user indeed significantly deviated from usual behavior, but there's no potential breach.
734-
735-
1. **FP** (Unusual behavior): If you're able to confirm that the user legitimately performed the unusual activities, or more activities than the established baseline.
736-
737-
**Recommended action**: Dismiss the alert.
738-
739-
**Understand the scope of the breach**
740-
741-
1. Review all user activity and alerts for additional indicators of compromise.
742-
743-
#### Deprecation timeline
744-
745-
We're gradually retiring the **Investigation priority score increase** alert from Microsoft Defender for Cloud Apps by August 2024.
746-
747-
After careful analysis and consideration, we decided to deprecate it due to the high rate of false positives associated with this alert, which we found wasn't contributing effectively to the overall security of your organization.
748-
749-
Our research indicated that this feature wasn't adding significant value and wasn't aligned with our strategic focus on delivering high-quality, reliable security solutions.
750-
751-
We're committed to continuously improving our services and ensuring that they meet your needs and expectations.
752-
753-
For those who wish to continue using this alert, we suggest using the following advanced hunting query instead as a suggested template. Modify the query based on your needs.
754-
755-
```kql
756-
let time_back = 1d;
757-
let last_seen_threshold = 30;
758-
// the number of days which the resource is considered to be in use by the user lately, and therefore not indicates anomaly resource usage
759-
// anomaly score based on LastSeenForUser column in CloudAppEvents table
760-
let last_seen_scores =
761-
CloudAppEvents
762-
| where Timestamp > ago(time_back)
763-
| where isnotempty(LastSeenForUser)
764-
| mv-expand LastSeenForUser
765-
| extend resource = tostring(bag_keys(LastSeenForUser)[0])
766-
| extend last_seen = LastSeenForUser[resource]
767-
| where last_seen < 0 or last_seen > last_seen_threshold
768-
// score is calculated as the number of resources which were never seen before or breaching the chosen threshold
769-
| summarize last_seen_score = dcount(resource) by ReportId, AccountId;
770-
// anomaly score based on UncommonForUser column in CloudAppEvents table
771-
let uncommonality_scores =
772-
CloudAppEvents
773-
| where Timestamp > ago(time_back)
774-
| where isnotempty(UncommonForUser)
775-
| extend uncommonality_score = array_length(UncommonForUser)
776-
// score is calculated as the number of uncommon resources on the event
777-
| project uncommonality_score, ReportId, AccountId;
778-
last_seen_scores | join kind=innerunique uncommonality_scores on ReportId and AccountId
779-
| project-away ReportId1, AccountId1
780-
| extend anomaly_score = last_seen_score + uncommonality_score
781-
// joined scores
782-
```
783722

784723
## See also
785724

File renamed without changes.
File renamed without changes.

defender-xdr/microsoft-365-security-center-defender-cloud-apps.md renamed to CloudAppSecurityDocs/microsoft-365-security-center-defender-cloud-apps.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -26,26 +26,26 @@ ms.custom: admindeeplinkDEFENDER
2626

2727
**Applies to:**
2828

29-
- [Microsoft Defender XDR](microsoft-365-defender.md)
29+
- [Microsoft Defender XDR](/defender-xdr/microsoft-365-defender)
3030
- [Microsoft Defender for Cloud Apps](/defender-cloud-apps/)
3131

3232
Microsoft Defender for Cloud Apps is available inside the Microsoft Defender portal. The Defender portal is the home for monitoring and managing security across your Microsoft identities, data, devices, apps, and infrastructure, allowing security admins to perform their security tasks in one location, across multiple Microsoft Defender services.
3333

3434
SOC analysts can triage, investigate, and hunt across all Microsoft Defender XDR workloads, including cloud apps.
3535

36-
Take a look in Microsoft Defender XDR at <https://security.microsoft.com>.
36+
Take a look in the Microsoft Defender portal at <https://security.microsoft.com>.
3737

38-
Learn more about the benefits: [Overview of Microsoft Defender XDR](microsoft-365-defender.md).
38+
Learn more about the benefits: [Overview of Microsoft Defender XDR](/defender-xdr/microsoft-365-defender).
3939

4040
## Perform cloud app security tasks
4141

4242
Find Defender for Cloud Apps functionality in the Microsoft Defender portal under **Cloud Apps**. For example:
4343

44-
:::image type="content" source="media/defender-for-cloud-apps/cloud-apps.png" alt-text="Screenshot that shows the Defender for Cloud Apps Cloud discovery page." lightbox="media/defender-for-cloud-apps/cloud-apps.png":::
44+
:::image type="content" source="media/microsoft-365-security-center-defender-cloud-apps/cloud-apps.png" alt-text="Screenshot that shows the Defender for Cloud Apps Cloud discovery page." lightbox="media/microsoft-365-security-center-defender-cloud-apps/cloud-apps.png":::
4545

4646
## Investigate cloud app alerts
4747

48-
Defender for Cloud Apps alerts show in the Defender portal's incident and alerts queues, with relevant content inside alert pages for each type of an alert. For more information, see [Investigate incidents in Microsoft Defender XDR](investigate-incidents.md).
48+
Defender for Cloud Apps alerts show in the Defender portal's incident and alerts queues, with relevant content inside alert pages for each type of an alert. For more information, see [Investigate incidents in Microsoft Defender XDR](/defender-xdr/investigate-incidents).
4949

5050
## Global search for your connected cloud apps
5151

@@ -57,7 +57,7 @@ Use the Microsoft Defender portal's global search bar at the top of the page to
5757

5858
Use the **Assets > Identities** page to find comprehensive details about entities pulled from connected cloud applications, including a users's activity history and security alerts related to the user. For example:
5959

60-
:::image type="content" source="media/defender-for-cloud-apps/dashboard-top-users.png" alt-text="Screenshot that shows cloud app entities in the Identities page." lightbox="media/defender-for-cloud-apps/dashboard-top-users.png":::
60+
:::image type="content" source="media/microsoft-365-security-center-defender-cloud-apps/dashboard-top-users.png" alt-text="Screenshot that shows cloud app entities in the Identities page." lightbox="media/microsoft-365-security-center-defender-cloud-apps/dashboard-top-users.png":::
6161

6262
<a name='redirection-from-the-classic-microsoft-defender-for-cloud-apps-portal-to-microsoft-365-defender'></a>
6363

@@ -76,9 +76,9 @@ Learn how to protect your cloud apps in Microsoft Defender XDR:
7676
> [!VIDEO https://learn.microsoft.com/_themes/docs.theme/master/en-us/_themes/global/video-embed.html?id=2105e5c9-23bf-41fb-a61d-0f0fae8ef05f title="Defender for Cloud Apps in Microsoft Defender XDR for customers migrating from the classic portal"]
7777
7878

79-
## Related information
79+
## Related content
8080

81-
- [Microsoft Defender XDR](microsoft-365-defender.md)
82-
- [Investigate incidents in Microsoft Defender XDR](investigate-incidents.md)
81+
- [Microsoft Defender XDR](/defender-xdr/microsoft-365-defender)
82+
- [Investigate incidents in Microsoft Defender XDR](/defender-xdr/investigate-incidents)
8383
- [Contact support](/defender-cloud-apps/support-and-ts)
8484
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

CloudAppSecurityDocs/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ items:
77
href: what-is-defender-for-cloud-apps.md
88
- name: What's new in Defender for Cloud Apps
99
href: release-notes.md
10+
- name: Defender for Cloud Apps in the Microsoft Defender portal
11+
href: microsoft-365-security-center-defender-cloud-apps.md
1012
- name: Privacy with Defender for Cloud Apps
1113
href: cas-compliance-trust.md
1214
- name: Preview features
@@ -31,6 +33,8 @@ items:
3133
href: best-practices.md
3234
- name: Deploy Defender for Cloud Apps
3335
items:
36+
- name: Pilot and deploy Microsoft Defender XDR
37+
href: /defender-xdr/pilot-deploy-overview?toc=/cloud-app-security/toc.json&bc=/cloud-app-security/breadcrumb/toc.json
3438
- name: Network requirements
3539
href: network-requirements.md
3640
- name: Getting started

CloudAppSecurityDocs/tutorial-ueba.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,6 @@ Defender for Cloud Apps uses the following to measure risk:
4646

4747
Select the investigation priority score for an alert or an activity to view the evidence that explains how Defender for Cloud Apps scored the activity.
4848

49-
> [!NOTE]
50-
> We're gradually retiring the [**Investigation priority score increase**](investigate-anomaly-alerts.md#investigation-priority-score-increase-preview) alert from Microsoft Defender for Cloud Apps by August 2024. The investigation priority score and the procedure described in this article are not affected by this change.
51-
>
52-
> For more information, see [Investigation priority score increase deprecation timeline](investigate-anomaly-alerts.md#deprecation-timeline).
53-
54-
5549
## Phase 1: Connect to the apps you want to protect<a name="connect-apps-protect"></a>
5650

5751
Connect at least one app to Microsoft Defender for Cloud Apps using the [API connectors](enable-instant-visibility-protection-and-governance-actions-for-your-apps.md). We recommend that you start by connecting [Microsoft 365](./connect-office-365.md).

defender-endpoint/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -511,6 +511,8 @@
511511
href: troubleshoot-collect-support-log.md
512512
- name: Troubleshoot Microsoft Defender Antivirus settings
513513
href: troubleshoot-settings.md
514+
- name: Troubleshoot Microsoft Defender Antivirus service startup problems
515+
href: troubleshoot-service-startup-problems.md
514516
- name: Troubleshooting Security Intelligence Updates from Microsoft Update source
515517
href: security-intelligence-update-tshoot.md
516518
displayName: Troubleshooting Security Intelligence Updates from Microsoft Update source

0 commit comments

Comments
 (0)