Skip to content

Commit c535114

Browse files
Merge pull request #5625 from MicrosoftDocs/main
[AutoPublish] main to live - 11/17 07:33 PST | 11/17 21:03 IST
2 parents 636fbc2 + 9e0cfa0 commit c535114

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

defender-for-cloud-apps/troubleshooting-cloud-discovery.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This article provides a list of cloud discovery errors and resolution recommenda
1212

1313
Even after Discovery is set up, customers might continue hardening the Operating System in order to meet compliance standards. However, this action might cause interference with the containerization service itself.
1414

15-
## Microsoft Defender for Endpoint integration
15+
## Microsoft Defender for Endpoint integration errors
1616

1717
If you integrated Microsoft Defender for Endpoint with Defender for Cloud Apps, and you don't see the results of the integration.
1818

@@ -37,6 +37,8 @@ You can track the processing of cloud discovery logs using the governance log. T
3737

3838
## Log collector errors
3939

40+
The [Log collector Diagnostic script](https://github.com/microsoft/Microsoft-Defender-for-Cloud-Apps/tree/main/Sample%20scripts/Log-Collector-Diag-Script) automates the collection and compression of logs and diagnostic data for troubleshooting Log Collector containers on Linux (Docker/Podman) to improve workflow efficiency. If you need to contact support, run the script and share the generated log bundle for faster case resolution.
41+
4042
|Issue|Resolution|
4143
|----|----|
4244
|Couldn't connect to the log collector over FTP| 1. Verify that you're using FTP credentials and not SSH credentials. <br />2. Verify that the FTP client you're using isn't set to SFTP (Secure File Transfer Protocol). |

defender-xdr/incident-queue.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Select **Most recent incidents and alerts** to toggle a timeline chart of the nu
4040

4141
:::image type="content" source="./media/incidents-queue/most-recent-incidents.png" alt-text="Screenshot of 24-hour incident graph." lightbox="./media/incidents-queue/most-recent-incidents.png":::
4242

43-
The incident queue includes Defender Queue Assistant that helps security teams cut through the large number of incidents and focus on the incidents that matter most. Using a machine learning prioritization algorithm, the Queue Assistant surfaces the highest-priority incidents, explains the reasoning behind the prioritization, and provides intuitive tools for sorting and filtering the incident queue. The algorithm is runs for all alerts, Microsoft native alerts, custom detections, or third-party signals. The algorithm is trained on real-world anonymized data and considers, among other things, the following data points when calculating the priority score:
43+
The incident queue includes Defender Queue Assistant that helps security teams cut through the large number of incidents and focus on the incidents that matter most. Using a machine learning prioritization algorithm, the Queue Assistant surfaces the highest-priority incidents, explains the reasoning behind the prioritization, and provides intuitive tools for sorting and filtering the incident queue. The algorithm runs for all alerts, Microsoft native alerts, custom detections, or third-party signals. The algorithm is trained on real-world anonymized data and considers, among other things, the following data points when calculating the priority score:
4444
+ Attack disruption signals
4545
+ Threat analytics
4646
+ Severity

0 commit comments

Comments
 (0)