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/best-practices.md
+18-8Lines changed: 18 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,8 @@ The best practices discussed in this article include:
30
30
Integrating Defender for Cloud Apps with Microsoft Defender for Endpoint gives you the ability to use cloud discovery beyond your corporate network or secure web gateways. With the combined user and device information, you can identify risky users or devices, see what apps they are using, and investigate further in the Defender for Endpoint portal.
31
31
32
32
**Best practice**: Enable Shadow IT Discovery using Defender for Endpoint
33
-
**Detail**: Cloud discovery analyzes traffic logs collected by Defender for Endpoint, Firewall and Secure Web Gateways and assesses identified apps against the cloud app catalog to provide compliance and security information. By configuring cloud discovery, you gain visibility into cloud use, Shadow IT, and continuous monitoring of the unsanctioned apps being used by your users.
33
+
**Detail**: Cloud discovery analyzes traffic logs collected by Defender for Endpoint, Firewall and Secure Web Gateways and assesses identified apps against the cloud app catalog to provide compliance and security information. By configuring cloud discovery, you gain visibility into cloud use, Shadow IT, and continuous monitoring of the unsanctioned apps being used by your users.
34
+
34
35
**For more information**:
35
36
36
37
*[Microsoft Defender for Endpoint integration with Defender for Cloud Apps](mde-integration.md)
@@ -40,7 +41,7 @@ Integrating Defender for Cloud Apps with Microsoft Defender for Endpoint gives y
40
41
---
41
42
42
43
**Best practice**: Configure App Discovery policies to proactively identify risky, non-compliant, and trending apps
43
-
**Details**: App Discovery policies make it easier to track of the significant discovered applications in your organization to help you manage these applications efficiently. Create policies to receive alerts when detecting new apps that are identified as either risky, non-compliant, trending, or high-volume.
44
+
**Detail**: App Discovery policies make it easier to track of the significant discovered applications in your organization to help you manage these applications efficiently. Create policies to receive alerts when detecting new apps that are identified as either risky, non-compliant, trending, or high-volume.
@@ -53,6 +54,7 @@ Integrating Defender for Cloud Apps with Microsoft Defender for Endpoint gives y
53
54
**Detail**: Many users casually grant OAuth permissions to third-party apps to access their account information and, in doing so, inadvertently also give access to their data in other cloud apps. Usually, IT has no visibility into these apps making it difficult to weigh the security risk of an app against the productivity benefit that it provides.
54
55
55
56
Defender for Cloud Apps provides you with the ability to investigate and monitor the app permissions your users granted. You can use this information to identify a potentially suspicious app and, if you determine that it is risky, you can ban access to it.
57
+
56
58
**For more information**:
57
59
58
60
*[Manage OAuth apps](manage-app-permissions.md)
@@ -73,7 +75,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
73
75
## Limit exposure of shared data and enforce collaboration policies
74
76
75
77
**Best practice**: Connect Microsoft 365
76
-
**Detail**: Connecting Microsoft 365 to Defender for Cloud Apps gives you immediate visibility into your users' activities, files they are accessing, and provides governance actions for Microsoft 365, SharePoint, OneDrive, Teams, Power BI, Exchange, and Dynamics.
78
+
**Detail**: Connecting Microsoft 365 to Defender for Cloud Apps gives you immediate visibility into your users' activities, files they are accessing, and provides governance actions for Microsoft 365, SharePoint, OneDrive, Teams, Power BI, Exchange, and Dynamics.
@@ -91,7 +94,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
91
94
---
92
95
93
96
**Best practice**: Create policies to remove sharing with personal accounts
94
-
**Detail**: Connecting Microsoft 365 to Defender for Cloud Apps gives you immediate visibility into your users' activities, files they are accessing, and provides governance actions for Microsoft 365, SharePoint, OneDrive, Teams, Power BI, Exchange, and Dynamics.
97
+
**Detail**: Connecting Microsoft 365 to Defender for Cloud Apps gives you immediate visibility into your users' activities, files they are accessing, and provides governance actions for Microsoft 365, SharePoint, OneDrive, Teams, Power BI, Exchange, and Dynamics.
@@ -101,7 +105,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
101
105
## Discover, classify, label, and protect regulated and sensitive data stored in the cloud
102
106
103
107
**Best practice**: Integrate with Microsoft Purview Information Protection
104
-
**Detail**: Integrating with Microsoft Purview Information Protection gives you the capability to automatically apply sensitivity labels and optionally add encryption protection. Once the integration is turned on, you can apply labels as a governance action, view files by classification, investigate files by classification level, and create granular policies to make sure classified files are being handled properly. If you do not turn on the integration, you cannot benefit from the ability to automatically scan, label, and encrypt files in the cloud.
108
+
**Detail**: Integrating with Microsoft Purview Information Protection gives you the capability to automatically apply sensitivity labels and optionally add encryption protection. Once the integration is turned on, you can apply labels as a governance action, view files by classification, investigate files by classification level, and create granular policies to make sure classified files are being handled properly. If you do not turn on the integration, you cannot benefit from the ability to automatically scan, label, and encrypt files in the cloud.
109
+
105
110
**For more information**:
106
111
107
112
*[Microsoft Purview Information Protection integration](azip-integration.md)
@@ -128,7 +133,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
128
133
## Enforce DLP and compliance policies for data stored in the cloud
129
134
130
135
**Best practice**: Protect confidential data from being shared with external users
131
-
**Detail**: Create a file policy that detects when a user tries to share a file with the **Confidential** sensitivity label with someone external to your organization, and configure its governance action to remove external users. This policy ensures your confidential data doesn't leave your organization and external users cannot gain access to it.
136
+
**Detail**: Create a file policy that detects when a user tries to share a file with the **Confidential** sensitivity label with someone external to your organization, and configure its governance action to remove external users. This policy ensures your confidential data doesn't leave your organization and external users cannot gain access to it.
@@ -139,6 +145,7 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
139
145
140
146
**Best practice**: Manage and control access to high risk devices
141
147
**Detail**: Use conditional access app control to set controls on your SaaS apps. You can create session policies to monitor your high risk, low trust sessions. Similarly, you can create session policies to block and protect downloads by users trying to access sensitive data from unmanaged or risky devices. If you don't create session policies to monitor high-risk sessions, you'll lose the ability to block and protect downloads in the web client, as well as the ability to monitor low-trust session both in Microsoft and third-party apps.
148
+
142
149
**For more information**:
143
150
144
151
*[Protect apps with Microsoft Defender for Cloud Apps Conditional Access app control](proxy-intro-aad.md)
@@ -187,7 +194,8 @@ Anomaly detection policies are triggered when there are unusual activities perfo
187
194
---
188
195
189
196
**Best practice**: Create OAuth app policies
190
-
**Detail**: Create an OAuth app policy to notify you when an OAuth app meets certain criteria. For example, you can choose to be notified when a specific app that requires a high permission level was accessed by more than 100 users.
197
+
**Detail**: Create an OAuth app policy to notify you when an OAuth app meets certain criteria. For example, you can choose to be notified when a specific app that requires a high permission level was accessed by more than 100 users.
198
+
191
199
**For more information**:
192
200
193
201
*[OAuth app policies](app-permission-policy.md)
@@ -201,7 +209,8 @@ Anomaly detection policies are triggered when there are unusual activities perfo
201
209
202
210
You can investigate an alert by selecting it on the **Alerts** page and reviewing the audit trail of activities relating to that alert. The audit trail gives you visibility into activities of the same type, same user, same IP address and location, to provide you with the overall story of an alert. If an alert warrants further investigation, create a plan to resolve these alerts in your organization.
203
211
204
-
When dismissing alerts, it's important to investigate and understand why they are of no importance or if they are false positives. If there is a high volume of such activities, you may also want to consider reviewing and tuning the policy triggering the alert.
212
+
When dismissing alerts, it's important to investigate and understand why they are of no importance or if they are false positives. If there is a high volume of such activities, you may also want to consider reviewing and tuning the policy triggering the alert.
213
+
205
214
**For more information**:
206
215
207
216
*[Activities](activity-filters.md)
@@ -212,6 +221,7 @@ When dismissing alerts, it's important to investigate and understand why they ar
212
221
213
222
**Best practice**: Connect Azure, AWS and GCP
214
223
**Detail**: Connecting each of these cloud platforms to Defender for Cloud Apps helps you improve your threat detections capabilities. By monitoring administrative and sign-in activities for these services, you can detect and be notified about possible brute force attack, malicious use of a privileged user account, and other threats in your environment. For example, you can identify risks such as unusual deletions of VMs, or even impersonation activities in these apps.
224
+
215
225
**For more information**:
216
226
217
227
-[Connect Azure to Microsoft Defender for Cloud Apps](protect-azure.md#connect-azure-to-microsoft-defender-for-cloud-apps)
0 commit comments