Skip to content

Commit 162fe3a

Browse files
committed
Update best-practices.md
1 parent 2600d48 commit 162fe3a

File tree

1 file changed

+2
-27
lines changed

1 file changed

+2
-27
lines changed

CloudAppSecurityDocs/best-practices.md

Lines changed: 2 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The best practices discussed in this article include:
3030
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.
3131

3232
**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.
3434
**For more information**:
3535

3636
* [Microsoft Defender for Endpoint integration with Defender for Cloud Apps](mde-integration.md)
@@ -59,7 +59,6 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
5959
* [OAuth app policies](app-permission-policy.md)
6060

6161
---
62-
<br/><br/>
6362

6463
## Apply cloud governance policies
6564

@@ -126,18 +125,6 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
126125

127126
---
128127

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.
131-
**For more information**:
132-
133-
* [Connect apps](enable-instant-visibility-protection-and-governance-actions-for-your-apps.md)
134-
* [File policies](data-protection-policies.md)
135-
* [Content inspection](content-inspection.md)
136-
137-
---
138-
<br/><br/>
139-
140-
141128
## Enforce DLP and compliance policies for data stored in the cloud
142129

143130
**Best practice**: Protect confidential data from being shared with external users
@@ -147,8 +134,6 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
147134
* [Governing connected apps](governance-actions.md)
148135

149136
---
150-
<br/><br/>
151-
152137

153138
## Block and protect download of sensitive data to unmanaged or risky devices
154139

@@ -160,8 +145,6 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
160145
* [Session policies](session-policy-aad.md)
161146

162147
---
163-
<br/><br/>
164-
165148

166149
## Secure collaboration with external users by enforcing real-time session controls
167150

@@ -173,8 +156,6 @@ Defender for Cloud Apps provides you with the ability to investigate and monitor
173156
* [Session policies](session-policy-aad.md)
174157

175158
---
176-
<br/><br/>
177-
178159

179160
## Detect cloud threats, compromised accounts, malicious insiders, and ransomware
180161

@@ -187,9 +168,7 @@ Anomaly detection policies are triggered when there are unusual activities perfo
187168

188169
* **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.
189170

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.
171+
* **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.
193172

194173
**For more information**:
195174

@@ -214,8 +193,6 @@ Anomaly detection policies are triggered when there are unusual activities perfo
214193
* [OAuth app policies](app-permission-policy.md)
215194

216195
---
217-
<br/><br/>
218-
219196

220197
## Use the audit trail of activities for forensic investigations
221198

@@ -230,8 +207,6 @@ When dismissing alerts, it's important to investigate and understand why they ar
230207
* [Activities](activity-filters.md)
231208

232209
---
233-
<br/><br/>
234-
235210

236211
## Secure IaaS services and custom apps
237212

0 commit comments

Comments
 (0)