Skip to content

Commit f07718d

Browse files
authored
Merge pull request #2032 from MicrosoftDocs/main
Published main to live, Wednesday 5:00 PM IST, 11/27
2 parents 23eacdc + cbe14de commit f07718d

28 files changed

+506
-208
lines changed

CloudAppSecurityDocs/app-governance-app-policies-create.md

Lines changed: 46 additions & 45 deletions
Large diffs are not rendered by default.

CloudAppSecurityDocs/app-governance-app-policies-get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ description: Get started learning about app governance policies with Microsoft D
77

88
# Get started with app policies
99

10-
Policies for app governance are a way to implement proactive and reactive alerts and automatic remediation for your specific needs for app compliance in your organization. You can create policies in app governance to manage OAuth apps in Microsoft Entra ID, Google and Salesforce.
10+
Policies for app governance are a way to implement proactive and reactive alerts and automatic remediation for your specific needs for app compliance in your organization. You can create policies in app governance to manage OAuth apps in Microsoft 365, Google and Salesforce.
1111

1212
There are two types of policies in app governance:
1313

CloudAppSecurityDocs/app-governance-app-policies-manage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,14 @@ description: Manage your app governance policies.
77

88
# Manage app policies
99

10-
Use app governance to manage OAuth policies for Microsoft Entra ID, Google Workspace, and Salesforce.
10+
Use app governance to manage OAuth policies for Microsoft 365, Google Workspace, and Salesforce.
1111

1212
You might need to manage your app policies as follows to keep up-to-date with your organization's apps, respond to new app-based attacks, and for ongoing changes to your app compliance needs:
1313

1414
- Create new policies targeted at new apps
1515
- Change the status of an existing policy (active, inactive, audit mode)
1616
- Change the conditions of an existing policy
17-
- Change the actions of an existing policy for autoremediation of alerts
17+
- Change the actions of an existing policy for auto-remediation of alerts
1818

1919
<a name='manage-oauth-app-policies-for-azure-ad'></a>
2020

CloudAppSecurityDocs/app-governance-get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Before you start, verify that you satisfy the following prerequisites:
1717

1818
- Microsoft Defender for Cloud Apps must be present in your account as either a standalone product or as part of the various [license](#licensing) packages.
1919

20-
If you aren't already a Defender for Cloud Apps customer, you can [sign up for a free trial](https://www.microsoft.com/security/business/cloud-apps-defender).
20+
If you aren't already a Defender for Cloud Apps customer, you can [sign up for a free trial](https://www.microsoft.com/security/business/cloud-apps-defender).
2121

2222
- You must have [one of the appropriate roles](#roles) to turn on app governance and access it.
2323

CloudAppSecurityDocs/app-governance-visibility-insights-compliance-posture.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -19,41 +19,41 @@ The **Overview** page shows the following details:
1919
For example:
2020

2121
> [!div class="mx-imgBorder"]
22-
>![Relative number of detected and policy-based incidents.](incidents-summary1.png)
23-
>
22+
> ![Relative number of detected and policy-based incidents.](incidents-summary1.png)
23+
>
2424
> [!div class="mx-imgBorder"]
25-
>![top alerts.](media/app-governance-visibility-insights-compliance-posture/top-alerts.png)
25+
> ![top alerts.](media/app-governance-visibility-insights-compliance-posture/top-alerts.png)
2626
2727
## Data usage cards
2828

2929
Data usage cards show the following types of information:
3030

31-
- **Total data accessed by apps** in the tenant through Graph API over the current month and previous three calendar months. (Currently includes emails, files, and chat and channel messages read and written by apps that access Microsoft 365 using Graph API)
31+
- **Total data accessed by apps** in the tenant through Microsoft Graph and EWS APIs over the current month and previous three calendar months. (Currently includes emails, files, and chat and channel messages read and written by apps that access Microsoft 365 using Microsoft Graph and EWS APIs)
3232

33-
- **Data usage over the current month and previous three calendar months**, broken down by resource type. (Currently includes emails, files, and chat and channel messages read and written by apps that access Microsoft 365 using Graph API)
33+
- **Data usage over the current month and previous three calendar months**, broken down by resource type. (Currently includes emails, files, and chat and channel messages read and written by apps that access Microsoft 365 using Microsoft Graph and EWS APIs)
3434

3535
For example:
3636

3737
> [!div class="mx-imgBorder"]
38-
>![Total data accessed by apps.](media/app-governance-visibility-insights-compliance-posture/data-usage-chart.png)
38+
> ![Total data accessed by apps.](media/app-governance-visibility-insights-compliance-posture/data-usage-chart.png)
3939
4040
## Apps that access data on Microsoft 365
4141

42-
For apps that access data on Microsoft 365, cards show the number of apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams in the last 30 days
42+
For apps that access data on Microsoft 365, cards show the number of apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams using Microsoft Graph and EWS APIs in the last 30 days.
4343

4444
For example:
4545

4646
> [!div class="mx-imgBorder"]
47-
>![Apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams in the last 30 days.](media/app-governance-visibility-insights-compliance-posture/apps-accessed-m365-services-chart.png)
47+
> ![Apps that have accessed data on SharePoint, OneDrive, Exchange Online, or Teams in the last 30 days.](media/app-governance-visibility-insights-compliance-posture/apps-accessed-m365-services-chart.png)
4848
4949
## Sensitivity labels accessed
5050

51-
For sensitivity labeling data, cards show the number apps that have accessed content with sensitivity labels on SharePoint, OneDrive, Exchange Online or Teams in the last 30 days.
51+
For sensitivity labeling data, cards show the number apps that have accessed content with sensitivity labels on SharePoint, OneDrive, Exchange Online or Teams using Microsoft Graph and EWS APIs in the last 30 days.
5252

5353
For example:
5454

5555
> [!div class="mx-imgBorder"]
56-
>![number apps that have accessed content with sensitivity labels.](sensitive-data-accessed-chart1.png)
56+
> ![number apps that have accessed content with sensitivity labels.](sensitive-data-accessed-chart1.png)
5757
5858
## Next steps
5959

CloudAppSecurityDocs/app-governance-visibility-insights-get-started.md

Lines changed: 37 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -38,32 +38,48 @@ One of the primary value points for app governance is the ability to quickly vie
3838
1. On the **App governance** page, select one of the apps tabs to display your apps.
3939

4040
The apps listed depend on the apps present in your tenant.
41-
41+
4242
1. Filter the apps listed using one or more of the following default filter options:
4343

44-
- **API access**
45-
- **Privilege level**
46-
- **Permission usage**
47-
- **Permission type**
48-
- **Publisher verified**
49-
44+
- **API access**
45+
46+
- **Privilege level**
47+
48+
- **Permission** (Preview)
49+
50+
- **Permission usage**
51+
52+
- **App origin**
53+
54+
- **Permission type**
55+
56+
- **Publisher verified**
57+
5058
Use one of the following nondefault filters to further customize the apps listed:
51-
52-
- **Last modified**
53-
- **Added on**
54-
- **Certification**
55-
- **Users**
56-
- **Services accessed**
57-
- **Data usage**
58-
- **Sensitivity labels accessed**
59-
60-
> [!TIP]
61-
> Save the query to save the currently selected filters for use again in the future.
62-
59+
60+
- **Last modified**
61+
62+
- **Added on**
63+
64+
- **Certification**
65+
66+
- **Users**
67+
68+
- **Services accessed**
69+
70+
- **Data usage**
71+
72+
- **Sensitivity labels accessed**
73+
74+
> [!TIP]
75+
> Save the query to save the currently selected filters for use again in the future.
76+
6377
1. Select the name of an app to view more details. For example:
6478

65-
:::image type="content" source="media/app-governance-visibility-insights-get-started/image2.png" alt-text="Screenshot of an app details pane showing an app summary.":::
66-
79+
![Screenshot of an app details pane showing an app summary.](media/app-governance-visibility-insights-get-started/app-governance-app-list-view.png)
80+
81+
82+
6783
The details pane lists the app usage over the past 30 days, the users who have consented to the app, and the permissions assigned to the app.
6884

6985
For example, an administrator might review the activity and permissions of an app that is generating alerts and make a decision to disable the app using the **Disable App** button towards the bottom of the app details pane.

CloudAppSecurityDocs/app-governance-visibility-insights-view-apps.md

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -17,21 +17,21 @@ For a summary of apps in your tenant, in Microsoft 365, go to **Cloud app > App
1717

1818
For example:
1919

20-
:::image type="content" source="media/app-governance-visibility-insights-view-apps/appg-cc-apps.png" alt-text="Screenshot of the Azure AD apps tab on the App governance page.":::
21-
20+
:::image type="content" source="media/app-governance-visibility-insights-view-apps/app-governance-app-list-view-new.png" alt-text="Screenshot of the Azure AD apps tab on the App governance page.":::
2221

2322
>[!NOTE]
2423
> Your sign-in account must have one of [these roles](app-governance-get-started.md#roles) to view any app governance data.
2524
>
2625
27-
On the **Azure AD apps** tab, the apps in your tenant are listed with the following details:
26+
On the **Microsoft 365** tab, the apps in your tenant are listed with the following details:
2827

2928
|Column name |Description |
3029
|---------|---------|
31-
|**App name** | The display name of the app as registered on Microsoft Entra ID |
32-
|**App status** | Shows whether the app is enabled or disabled, and if disabled by whom |
30+
| **App name** | The display name of the app as registered on Microsoft Entra ID |
31+
| **App status** | Shows whether the app is enabled or disabled, and if disabled by whom |
3332
| **Graph API access**| Shows whether the app has at least one Graph API permission |
3433
| **Permission type**| Shows whether the app has application (app only), delegated, or mixed permissions |
34+
| **App origin** (Preview)| Shows whether the app originated within the tenant or was registered in an external tenant |
3535
| **Consent type**| Shows whether the app consent has been given at the user or the admin level, and the number of users whose data is accessible to the app |
3636
| **Publisher**| Publisher of the app and their verification status |
3737
| **Last modified**| Date and time when registration information was last updated on Microsoft Entra ID |
@@ -55,13 +55,13 @@ You can also select **Search** to search for an app by name.
5555

5656
Select a specific app in the grid to view more details on an apps details pane on the right. For example:
5757

58-
:::image type="content" source="media/app-governance-visibility-insights-view-apps/image2.png" alt-text="Screenshot of an app details pane on the Azure AD tab.":::
58+
:::image type="content" source="media/app-governance-visibility-insights-view-apps/app-governance-app-list-view.png" alt-text="Screenshot of an app details pane on the Azure AD tab.":::
5959

60-
The **Summary** tab also shows more data about the app, such as the date first consented and the App ID. To see the properties of the app as registered in Microsoft Entra ID, select **View app in Azure AD**.
60+
The **Summary** tab also shows more data about the app, such as the date first consented and the App ID. To see the properties of the app as registered in Microsoft Entra ID, select **View in Microsoft Entra ID**.
6161

6262
In the details pane, select any of the following tabs to view more details:
6363

64-
- Select the **Data usage** tab to view a graph of data usage over time, for Exchange, SharePoint, OneDrive, and Teams resources. For example:
64+
- Select the **Data usage** tab to view a graph of data usage over time, for Exchange, SharePoint, OneDrive, and Teams resources via Microsoft Graph and EWS APIs. For example:
6565

6666
:::image type="content" source="media/app-governance-visibility-insights-view-apps/data-usage.png" alt-text="Screenshot of the Data usage tab.":::
6767

@@ -73,7 +73,7 @@ In the details pane, select any of the following tabs to view more details:
7373

7474
If an app is *admin consented*, the **Total consented users** are all users in the tenant.
7575

76-
- Select the **Permissions** tab to see a summary and list of the Graph API and legacy permissions granted to the app, consent type, and whether they are in use. For example:
76+
- Select the **Permissions** tab to see a summary and list of the Graph API and legacy permissions granted to the app, consent type, privilege level and whether they are in use. For example:
7777

7878
:::image type="content" source="media/app-governance-visibility-insights-view-apps/permissions.png" alt-text="Screenshot of the Permissions tab.":::
7979

@@ -83,13 +83,8 @@ In the details pane, select any of the following tabs to view more details:
8383

8484
:::image type="content" source="media/app-governance-visibility-insights-view-apps/sensitive-labels-details.png" alt-text="Screenshot of the Sensitivity labels tab.":::
8585

86-
For an enabled app, there's also a **Disable app** control to disable the use of the selected app and an **Enable app** control to enable the use of the disabled app. These actions require at least the following administrator roles:
87-
86+
For an enabled app, there's also a **Disable app** control to disable the use of the selected app and an **Enable app** control to enable the use of the disabled app. These actions require a *Company Administrator* administrator role.
8887

89-
- *Compliance Administrator*
90-
- *Company Administrator*
91-
- *Security Administrator*
92-
- *Security Operator*
9388

9489
## Managing Google Workspace and Salesforce OAuth apps
9590

CloudAppSecurityDocs/control-cloud-apps-with-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The following types of policies can be created:
2828
|![access policy icon.](media/proxy-policy.png)|Access policy|Conditional Access|Access policies provide you with real-time monitoring and control over user logins to your cloud apps. [Learn more](access-policy-aad.md)|
2929
|![session policy icon.](media/proxy-policy.png)|Session policy|Conditional Access|Session policies provide you with real-time monitoring and control over user activity in your cloud apps. [Learn more](session-policy-aad.md)|
3030
|![cloud discovery policy icon.](media/discovery-policy.png)|App discovery policy|Shadow IT|App discovery policies enable you to set alerts that notify you when new apps are detected within your organization. [Learn more](cloud-discovery-policies.md)|
31-
|![anomaly detection policy icon.](media/anomaly-detection-policy.png)|cloud discovery anomaly detection policy|Shadow IT|Cloud discovery anomaly detection policies look at the logs you use for discovering cloud apps and search for unusual occurrences. For example, when a user who never used Dropbox before suddenly uploads 600 GB to Dropbox, or when there are a lot more transactions than usual on a particular app. [Learn more](cloud-discovery-anomaly-detection-policy.md)|
31+
3232

3333
## Identifying risk
3434

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
title: Work with discovered apps via Graph API | Microsoft Defender for Cloud Apps
3+
description: Learn how to work with apps discovered by Microsoft Defender for Cloud Apps via Graph API.
4+
ms.topic: how-to #Don't change
5+
ms.date: 06/24/2024
6+
7+
#customer intent: As a security engineer, I want to work with discovered apps via API so that I can customize and automate the Microsoft Defender for Cloud Apps **Discovered apps** page functionality.
8+
9+
---
10+
11+
# Work with discovered apps via Graph API (Preview)
12+
13+
Microsoft Defender for Cloud Apps supports a Microsoft Graph API that you can use to work with discovered cloud apps, to customize and automate the **Discovered apps** page functionality in the Microsoft Defender portal.
14+
15+
This article provides sample procedures for using the [uploadedStreams API](/graph/api/security-datadiscoveryreport-list-uploadedstreams?view=graph-rest-beta) for common purposes.
16+
17+
## Prerequisites
18+
19+
Before you start using the Graph API, make sure to create an app and get an access token to use the application. Then, use the token to access the Defender for Cloud Apps API.
20+
21+
- Make sure to give the app permissions to access Defender for Cloud Apps, by granting it with `CloudApp-Discovery.Read.All` permissions and admin consent.
22+
23+
- Take note of your app secret and copy its value to use later on in your scripts.
24+
25+
You'll also need cloud app data streaming into Microsoft Defender for Cloud Apps.
26+
27+
For more information, see:
28+
29+
- [Manage admin access](manage-admins.md)
30+
- [Graph API authentication and authorization basics](/graph/auth/auth-concepts)
31+
- [Use the Microsoft Graph API](/graph/use-the-api)
32+
- [Set up Cloud Discovery](set-up-cloud-discovery.md)
33+
34+
## Get data about discovered apps
35+
36+
To get a high level summary of all the data available on your **Discovered apps** page, run the following GET command:
37+
38+
```http
39+
GET https://graph.microsoft.com/beta/dataDiscovery/cloudAppDiscovery/uploadedStreams
40+
```
41+
42+
To drill down to data for a specific stream:
43+
44+
1. Copy the relevant `<streamID>` value from the previous command's output.
45+
1. Run the following GET command using the `<streamID>` value:
46+
47+
```http
48+
GET https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams/<streamId>/aggregatedAppsDetails(period=duration'P90D')
49+
```
50+
51+
## Filter for a specific time period and risk score
52+
53+
Filter your API commands using `$select` and `$filter` to get data for a specific time period and risk score. For example, to view the names of all apps discovered in the last 30 days with a risk score lower or equal to 4, run:
54+
55+
```http
56+
GET https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams/<streamId>/aggregatedAppsDetails (period=duration'P30D')?$filter=riskRating  le 4 &$select=displayName
57+
```
58+
59+
## Get the userIdentifier of all users, devices, or IP addresses using a specific app
60+
61+
Identify the users, devices, or IP addresses that are currently using a specific app, run one of the following commands:
62+
63+
- **To return users**:
64+
65+
```http
66+
GET  https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams/<streamId>/aggregatedAppsDetails (period=duration'P30D')/ <id>/users
67+
```
68+
69+
- **To return IP addresses**:
70+
71+
```http
72+
GET  https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams/<streamId>/aggregatedAppsDetails (period=duration'P30D')/ <id>/ipAddress
73+
```
74+
75+
- **To return devices**:
76+
77+
```http
78+
GET  https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams/<streamId>/aggregatedAppsDetails (period=duration'P30D')/ <id>/name
79+
```
80+
81+
## Use filters to see apps by category
82+
83+
Use filters to see apps of a specific category, such as apps that are categorized as *Marketing*, and are also not HIPPA compliant. For example, run:
84+
85+
```http
86+
GET  https://graph.microsoft.com/beta/security/dataDiscovery/cloudAppDiscovery/uploadedStreams/<MDEstreamId>/aggregatedAppsDetails (period=duration 'P30D')?$filter= (appInfo/Hippa eq 'false') and category eq 'Marketing'
87+
```
88+
89+
## Related content
90+
91+
For more information, see [Working with discovered apps](discovered-apps.md) and the [Microsoft Graph API reference](/graph/api/resources/security-cloudappdiscovery-overview?view=graph-rest-beta).

0 commit comments

Comments
 (0)