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
+19-34Lines changed: 19 additions & 34 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 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,13 +54,13 @@ 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)
59
61
*[OAuth app policies](app-permission-policy.md)
60
62
61
63
---
62
-
<br/><br/>
63
64
64
65
## Apply cloud governance policies
65
66
@@ -74,7 +75,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
74
75
## Limit exposure of shared data and enforce collaboration policies
75
76
76
77
**Best practice**: Connect Microsoft 365
77
-
**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.
@@ -92,7 +94,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
92
94
---
93
95
94
96
**Best practice**: Create policies to remove sharing with personal accounts
95
-
**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.
@@ -102,7 +105,8 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
102
105
## Discover, classify, label, and protect regulated and sensitive data stored in the cloud
103
106
104
107
**Best practice**: Integrate with Microsoft Purview Information Protection
105
-
**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
+
106
110
**For more information**:
107
111
108
112
*[Microsoft Purview Information Protection integration](azip-integration.md)
@@ -126,42 +130,28 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
126
130
127
131
---
128
132
129
-
**Best practice**: Review reports in the **Files** page
130
-
**Detail**: Once you've connected various SaaS apps using app connectors, Defender for Cloud Apps scans files stored by these apps. In addition, each time a file is modified it is scanned again. You can use the **Files** page to understand and investigate the types of data being stored in your cloud apps. To help you investigate, you can filter by domains, groups, users, creation date, extension, file name and type, file ID, sensitivity label, and more. Using these filters puts you in control of how you choose to investigate files to make sure none of your data is at risk. Once you have a better understanding of how your data is being used, you can create policies to scan for sensitive content in these files.
## Enforce DLP and compliance policies for data stored in the cloud
142
134
143
135
**Best practice**: Protect confidential data from being shared with external users
144
-
**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.
## Block and protect download of sensitive data to unmanaged or risky devices
154
145
155
146
**Best practice**: Manage and control access to high risk devices
156
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
+
157
149
**For more information**:
158
150
159
151
*[Protect apps with Microsoft Defender for Cloud Apps Conditional Access app control](proxy-intro-aad.md)
160
152
*[Session policies](session-policy-aad.md)
161
153
162
154
---
163
-
<br/><br/>
164
-
165
155
166
156
## Secure collaboration with external users by enforcing real-time session controls
167
157
@@ -173,8 +163,6 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
173
163
*[Session policies](session-policy-aad.md)
174
164
175
165
---
176
-
<br/><br/>
177
-
178
166
179
167
## Detect cloud threats, compromised accounts, malicious insiders, and ransomware
180
168
@@ -187,9 +175,7 @@ Anomaly detection policies are triggered when there are unusual activities perfo
187
175
188
176
***Set IP Ranges**: Defender for Cloud Apps can identify known IP addresses once IP address ranges are set. With IP address ranges configured, you can tag, categorize, and customize the way logs and alerts are displayed and investigated. Adding IP address ranges helps to reduce false positive detections and improve the accuracy of alerts. If you choose not to add your IP addresses, you may see an increased number of possible false positives and alerts to investigate.
189
177
190
-
***Send Feedback for alerts**
191
-
192
-
When dismissing or resolving alerts, make sure to send feedback with the reason you dismissed the alert or how it's been resolved. This information assists Defender for Cloud Apps to improve our alerts and reduce false positives.
178
+
***Send Feedback for alerts**: When dismissing or resolving alerts, make sure to send feedback with the reason you dismissed the alert or how it's been resolved. This information assists Defender for Cloud Apps to improve our alerts and reduce false positives.
193
179
194
180
**For more information**:
195
181
@@ -208,14 +194,13 @@ Anomaly detection policies are triggered when there are unusual activities perfo
208
194
---
209
195
210
196
**Best practice**: Create OAuth app policies
211
-
**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
+
212
199
**For more information**:
213
200
214
201
*[OAuth app policies](app-permission-policy.md)
215
202
216
203
---
217
-
<br/><br/>
218
-
219
204
220
205
## Use the audit trail of activities for forensic investigations
221
206
@@ -224,19 +209,19 @@ Anomaly detection policies are triggered when there are unusual activities perfo
224
209
225
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.
226
211
227
-
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
+
228
214
**For more information**:
229
215
230
216
*[Activities](activity-filters.md)
231
217
232
218
---
233
-
<br/><br/>
234
-
235
219
236
220
## Secure IaaS services and custom apps
237
221
238
222
**Best practice**: Connect Azure, AWS and GCP
239
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
+
240
225
**For more information**:
241
226
242
227
-[Connect Azure to Microsoft Defender for Cloud Apps](protect-azure.md#connect-azure-to-microsoft-defender-for-cloud-apps)
0 commit comments