Skip to content

Commit ee310bc

Browse files
committed
updated metadata
1 parent e980057 commit ee310bc

6 files changed

+197
-18
lines changed
Lines changed: 184 additions & 0 deletions
Loading

defender-xdr/pilot-deploy-defender-cloud-apps.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,12 @@ ms.collection:
2020
- tier1
2121
ms.topic: concept-article
2222
#customerIntent: As a security admin, I want to pilot and deploy Microsoft Defender for Cloud Apps to evaluate it's ability to enhance my organization's security posture and protect against cloud application-based threats.
23-
23+
appliesto:
24+
- Microsoft Defender XDR
2425
---
2526

2627
# Pilot and deploy Microsoft Defender for Cloud Apps
2728

28-
**Applies to:**
29-
30-
- Microsoft Defender XDR
31-
3229
This article provides a workflow for piloting and deploying Microsoft Defender for Cloud Apps in your organization. Use these recommendations to onboard Microsoft Defender for Cloud Apps as part of an end-to-end solution with Microsoft Defender XDR.
3330

3431
This article assumes you have a production Microsoft 365 tenant and are piloting and deploying Microsoft Defender for Cloud Apps in this environment. This practice will maintain any settings and customizations you configure during your pilot for your [full deployment](/defender-cloud-apps/get-started).

defender-xdr/pilot-deploy-defender-endpoint.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ You start by evaluating the product or service and how it will work within your
5656

5757
Here is the workflow for piloting and deploying Defender for Endpoint in your production environment.
5858

59-
:::image type="content" source="./media/eval-defender-xdr/defender-endpoint-pilot-deploy-steps.png" alt-text="A diagram that shows the steps to pilot and deploy Microsoft Defender for Endpoint." lightbox="./media/eval-defender-xdr/defender-endpoint-pilot-deploy-steps.png" border="false":::
59+
:::image type="content" source="./media/eval-defender-xdr/defender-endpoint-pilot-deploy-steps.svg" alt-text="A diagram that shows the steps to pilot and deploy Microsoft Defender for Endpoint." lightbox="./media/eval-defender-xdr/defender-endpoint-pilot-deploy-steps.svg" border="false":::
6060

6161
Follow these steps:
6262

defender-xdr/pilot-deploy-defender-identity.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,13 +20,12 @@ ms.collection:
2020
- tier1
2121
ms.topic: concept-article
2222
#customerIntent: As a security admin, I want to pilot and deploy Microsoft Defender for Identity to evaluate it's ability to enhance my organization's security posture and protect against identity-based threats.
23+
appliesto:
24+
- Microsoft Defender XDR
2325
---
2426

2527
# Pilot and deploy Microsoft Defender for Identity
2628

27-
**Applies to:**
28-
- Microsoft Defender XDR
29-
3029
This article provides a workflow for piloting and deploying Microsoft Defender for Identity in your organization. Use these recommendations to onboard Microsoft Defender for Identity as part of an end-to-end solution with Microsoft Defender XDR.
3130

3231
This article assumes you have a production Microsoft 365 tenant and are piloting and deploying Microsoft Defender for Identity in this environment. This practice will maintain any settings and customizations you configure during your pilot for your [full deployment](/defender-for-identity/deploy/deploy-defender-identity).

defender-xdr/pilot-deploy-defender-office-365.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,16 +17,15 @@ ms.collection:
1717
- zerotrust-solution
1818
- highpri
1919
- tier1
20-
ms.topic: conceptual
20+
ms.topic: concept-article
2121
ms.date: 05/31/2024
22+
appliesto:
23+
- Microsoft Defender XDR
24+
#customer intent: To learn how to pilot and deploy Microsoft Defender for Office 365 in your production Microsoft 365 tenant.
2225
---
2326

2427
# Pilot and deploy Defender for Office 365
2528

26-
**Applies to:**
27-
- Microsoft Defender XDR
28-
29-
3029
This article provides a workflow for piloting and deploying Microsoft Defender for Office 365 in your organization. You can use these recommendations to onboard Microsoft Defender for Office 365 as an individual cybersecurity tool or as part of an end-to-end solution with Microsoft Defender XDR.
3130

3231
This article assumes you have a production Microsoft 365 tenant and are piloting and deploying Microsoft Defender for Office 365 in this environment. This practice will maintain any settings and customizations you configure during your pilot for your full deployment.

defender-xdr/pilot-deploy-investigate-respond.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,14 @@ ms.collection:
1818
- zerotrust-solution
1919
- highpri
2020
- tier1
21-
ms.topic: conceptual
21+
ms.topic: concept-article
22+
#customer intent: To learn how to investigate and respond to attacks using Microsoft Defender XDR.
23+
appliesto:
24+
- Microsoft Defender XDR
2225
---
2326

2427
# Investigate and respond using Microsoft Defender XDR
2528

26-
**Applies to:**
27-
- Microsoft Defender XDR
28-
2929
This article outlines the process to create incidents with attack simulations and tutorials and use Microsoft Defender XDR to investigate and respond. Before starting this process, be sure you've reviewed the overall process for [piloting and deploying Microsoft Defender XDR](pilot-deploy-overview.md) and you have at least piloted some of the components of Microsoft Defender XDR.
3030

3131
An incident in Microsoft Defender XDR is a collection of correlated alerts and associated data that make up the story of an attack. Microsoft 365 services and apps create alerts when they detect a suspicious or malicious event or activity. Individual alerts provide valuable clues about a completed or ongoing attack. However, attacks typically employ various techniques against different types of entities, such as devices, users, and mailboxes. The result is multiple alerts for multiple entities in your tenant.

0 commit comments

Comments
 (0)