Skip to content

Commit e98f133

Browse files
Merge pull request #3214 from MicrosoftDocs/main
Publish main to live, 03/20/25, 10:30 AM PDT
2 parents 37c58e2 + 678af85 commit e98f133

14 files changed

+31
-16
lines changed

.openpublishing.redirection.defender-endpoint.json

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,8 +82,8 @@
8282
},
8383
{
8484
"source_path": "defender-endpoint/linux-support-rhel.md",
85-
"redirect_url": "/defender-endpoint/comprehensive-guidance-on-linux-deployment",
86-
"redirect_document_id": true
85+
"redirect_url": "/defender-endpoint/linux-installer-script",
86+
"redirect_document_id": false
8787
},
8888
{
8989
"source_path": "defender-endpoint/pilot-deploy-defender-endpoint.md",
@@ -105,10 +105,15 @@
105105
"redirect_url": "/defender-endpoint/overview-client-analyzer",
106106
"redirect_document_id": false
107107
},
108+
{
109+
"source_path": "defender-endpoint/schedule-antivirus-scan-in-mde.md",
110+
"redirect_url": "/defender-endpoint/schedule-antivirus-scan-anacron",
111+
"redirect_document_id": true
112+
},
108113
{
109114
"source_path": "defender-endpoint/comprehensive-guidance-on-linux-deployment.md",
110115
"redirect_url": "/defender-endpoint/linux-installer-script",
111116
"redirect_document_id": true
112-
}
117+
}
113118
]
114119
}

CloudAppSecurityDocs/cas-compliance-trust.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Defender for Cloud Apps operates in the Microsoft Azure data centers in the foll
2929
|---------|---------|
3030
|**Customers whose tenants are provisioned in the United States** | United States |
3131
|**Customers whose tenants are provisioned in the European Union or the United Kingdom** | Either the European Union and/or the United Kingdom |
32-
|**Customers whose tenants are provisioned in any other region** | The United States and/or a data center in the region that's nearest to the location of where the customer's Microsoft Entra tenant has been provisioned |
32+
|**Customers whose tenants are provisioned in any other region** | The United States and/or a data center in the region that's nearest to the location of where the customer's Microsoft Entra tenant has been provisioned. |
3333

3434
In addition to the locations above, the App Governance features within Defender for Cloud Apps operate in the Microsoft Azure data centers in the following geographical regions listed below. Customer with App Governance enabled will have data stored within the data storage location the customer provisions in above, and in a second data storage location as described below:
3535

@@ -45,7 +45,7 @@ In addition to the locations above, the App Governance features within Defender
4545
| **Customers whose tenants are provisioned in Japan** | Japan |
4646
| **Customers whose tenants are provisioned in India** | India |
4747
| **Customers whose tenants are provisioned in Asia Pacific** | Asia Pacific |
48-
|**Customers whose tenants are provisioned in any other region** | The United States and/or a data center in the region that's nearest to the location of where the customer's Microsoft Entra tenant has been provisioned |
48+
|**Customers whose tenants are provisioned in any other region** | The United States and/or a data center in the region that's nearest to the location of where the customer's Microsoft Entra tenant has been provisioned. |
4949

5050
Customer data collected by Defender for Cloud Apps is either stored in your tenant location, as described in the previous tables, or in the geographic location of another online service that Defender for Cloud Apps shares data with, as defined by the data storage rules of that online service.
5151

@@ -71,4 +71,4 @@ Defender for Cloud Apps shares data, including customer data, among the followin
7171

7272
## Related content
7373

74-
For more information, see the [Microsoft Service Trust portal](https://www.microsoft.com/en-us/trust-center/product-overview).
74+
For more information, see the [Microsoft compliance offerings](/compliance/regulatory/offering-nist-sp-800-171).

defender-endpoint/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -294,7 +294,7 @@
294294
- name: Configure antivirus scans
295295
items:
296296
- name: Schedule antivirus scans using Anacron
297-
href: schedule-antivirus-scan-in-mde.md
297+
href: schedule-antivirus-scan-anacron.md
298298
- name: Schedule antivirus scans using Crontab
299299
href: linux-schedule-scan-mde.md
300300
- name: Network protection for Linux

defender-endpoint/linux-preferences.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protec
3636
| Settings | Description|
3737
|--|--|
3838
| 1. Configure static proxy discovery. | Configuring a static proxy helps ensure that telemetry is submitted and helps avoid network time-outs. Perform this task during and after your Defender for Endpoint installation. <br/><br/> See [Configure Microsoft Defender for Endpoint on Linux for static proxy discovery](linux-static-proxy-configuration.md). |
39-
| 2. Configure your antivirus scans. | You can schedule automatic antivirus scans by using either Anacron or Crontab. <br/><br/>See the following articles: <br/>- [Use Anacron to schedule an antivirus scan in Microsoft Defender for Endpoint on Linux](/defender-endpoint/schedule-antivirus-scan-in-mde)<br/>- [Use Crontab to schedule an antivirus scan in Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-schedule-scan-mde) |
39+
| 2. Configure your antivirus scans. | You can schedule automatic antivirus scans by using either Anacron or Crontab. <br/><br/>See the following articles: <br/>- [Use Anacron to schedule an antivirus scan in Microsoft Defender for Endpoint on Linux](/defender-endpoint/schedule-antivirus-scan-anacron)<br/>- [Use Crontab to schedule an antivirus scan in Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-schedule-scan-mde) |
4040
| 3. Configure your security settings and policies. | You can use the Microsoft Defender portal (Defender for Endpoint Security Settings Management) or a configuration profile (`.json` file) to configure Defender for Endpoint on Linux. Or, if you prefer, you can use command line to configure certain settings. <br/><br/> See the following articles:<br/>- [Defender for Endpoint Security Settings Management](linux-preferences.md#defender-for-endpoint-security-settings-management) <br/>- [Configuration profile](linux-preferences.md#configuration-profile)<br/>- [Command line](linux-resources.md#configure-from-the-command-line) |
4141
| 4. Configure and validate exclusions (as appropriate) | You can exclude certain files, folders, processes, and process-opened files from Defender for Endpoint on Linux. Global exclusions apply to real-time protection (RTP), behavior monitoring (BM), and endpoint detection and response (EDR), thus stopping all the associated antivirus detections, EDR alerts, and visibility for the excluded item.<br/><br/>See [Configure and validate exclusions for Microsoft Defender for Endpoint on Linux](linux-exclusions.md).|
4242
| 5. Configure the eBPF-based sensor. | The extended Berkeley Packet Filter (eBPF) for Microsoft Defender for Endpoint on Linux is automatically enabled for all customers by default for agent versions `101.23082.0006` and later. It provides supplementary event data for Linux operating systems and helps reduce the possibility of conflicts between applications. <br/><br/>See [Use eBPF-based sensor for Microsoft Defender for Endpoint on Linux](linux-support-ebpf.md). |

defender-endpoint/microsoft-defender-endpoint-linux.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 03/17/2025
18+
ms.date: 03/20/2025
1919
---
2020

2121
# Microsoft Defender for Endpoint on Linux
@@ -127,11 +127,7 @@ Additionally, they can use live response for a remote shell connection to perfor
127127

128128
Microsoft is committed to providing you with the information and controls you need to make choices about how your data is collected and used when you're using Defender for Endpoint on Linux.
129129

130-
For more information, see [Privacy for Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-privacy)
131-
132-
## Resources for troubleshooting, diagnostics, and configuration
133-
134-
If you run into any issues with Defender for Endpoint on Linux, or you just want some tips on configuring capabilities or exclusions, see [Resources](/defender-endpoint/linux-resources)
130+
For more information, see [Privacy for Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-privacy).
135131

136132
## Common applications that Defender for Endpoint impacts
137133

defender-endpoint/schedule-antivirus-scan-in-mde.md renamed to defender-endpoint/schedule-antivirus-scan-anacron.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: How to schedule an antivirus scan using Anacron in Microsoft Defender for Endpoint on Linux
2+
title: Schedule an antivirus scan using Anacron in Microsoft Defender for Endpoint on Linux
33
description: Learn how to schedule an antivirus scan in Microsoft Defender for Endpoint on Linux for better protection of your organization's assets.
44
ms.service: defender-endpoint
55
ms.author: deniseb

defender-xdr/advanced-hunting-deviceevents-table.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,8 @@ For information on other tables in the advanced hunting schema, [see the advance
103103
|`IsProcessRemoteSession` | `bool` | Indicates whether the created process was run under a remote desktop protocol (RDP) session (true) or locally (false) |
104104
| `ProcessRemoteSessionDeviceName` | `string` | Device name of the remote device from which the created process's RDP session was initiated |
105105
| `ProcessRemoteSessionIP` | `string` | IP address of the remote device from which the created process's RDP session was initiated |
106+
| `ProcessUniqueId` | `string` | Unique identifier of the process; this is equal to the Process Start Key in Windows devices |
107+
| `InitiatingProcessUniqueId` | `string` | Unique identifier of the initiating process; this is equal to the Process Start Key in Windows devices |
106108

107109

108110

defender-xdr/advanced-hunting-devicefileevents-table.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,8 @@ For information on other tables in the advanced hunting schema, [see the advance
9696
| `IsInitiatingProcessRemoteSession` | `bool` | Indicates whether the initiating process was run under a remote desktop protocol (RDP) session (true) or locally (false) |
9797
| `InitiatingProcessRemoteSessionDeviceName` | `string` | Device name of the remote device from which the initiating process's RDP session was initiated |
9898
| `InitiatingProcessRemoteSessionIP` | `string` | IP address of the remote device from which the initiating process's RDP session was initiated |
99+
| `ProcessUniqueId` | `string` | Unique identifier of the process; this is equal to the Process Start Key in Windows devices |
100+
| `InitiatingProcessUniqueId` | `string` | Unique identifier of the initiating process; this is equal to the Process Start Key in Windows devices |
99101

100102

101103
> [!NOTE]

defender-xdr/advanced-hunting-deviceimageloadevents-table.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,8 @@ For information on other tables in the advanced hunting schema, [see the advance
8080
| `IsInitiatingProcessRemoteSession` | `bool` | Indicates whether the initiating process was run under a remote desktop protocol (RDP) session (true) or locally (false) |
8181
| `InitiatingProcessRemoteSessionDeviceName` | `string` | Device name of the remote device from which the initiating process's RDP session was initiated |
8282
| `InitiatingProcessRemoteSessionIP` | `string` | IP address of the remote device from which the initiating process's RDP session was initiated |
83+
| `ProcessUniqueId` | `string` | Unique identifier of the process; this is equal to the Process Start Key in Windows devices |
84+
| `InitiatingProcessUniqueId` | `string` | Unique identifier of the initiating process; this is equal to the Process Start Key in Windows devices |
8385

8486

8587
## Related topics

defender-xdr/advanced-hunting-devicelogonevents-table.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,8 @@ For information on other tables in the advanced hunting schema, [see the advance
8989
| `IsInitiatingProcessRemoteSession` | `bool` | Indicates whether the initiating process was run under a remote desktop protocol (RDP) session (true) or locally (false) |
9090
| `InitiatingProcessRemoteSessionDeviceName` | `string` | Device name of the remote device from which the initiating process's RDP session was initiated |
9191
| `InitiatingProcessRemoteSessionIP` | `string` | IP address of the remote device from which the initiating process's RDP session was initiated |
92+
| `ProcessUniqueId` | `string` | Unique identifier of the process; this is equal to the Process Start Key in Windows devices |
93+
| `InitiatingProcessUniqueId` | `string` | Unique identifier of the initiating process; this is equal to the Process Start Key in Windows devices |
9294

9395

9496
> [!NOTE]

0 commit comments

Comments
 (0)