Merge branch 'main' into diannegali-updatethreatactorlist

Author: diannegali

defender-endpoint/android-configure.md

@@ -61,36 +61,32 @@ Network protection in Microsoft Defender for endpoint is disabled by default. Ad
 
 1. In the Microsoft Intune admin center, navigate to Apps > App configuration policies. Create a new App configuration policy.
 
-    > [!div class="mx-imgBorder"]
-    > ![Image of how to create a policy.](media/android-mem.png)
-
+> [!div class="mx-imgBorder"]
 1. Provide a name and description to uniquely identify the policy. Select **'Android Enterprise'** as the platform and **'Personally-owned work profile only'** as the profile type and **'Microsoft Defender'** as the Targeted app.
 
-    > [!div class="mx-imgBorder"]
-    > ![Image of policy details.](media/appconfigdetails.png)
-
+      > [!div class="mx-imgBorder"]
+   > ![Screenshot of policy details.](media/appconfigdetails.png)
+   
 1. In Settings page, select **'Use configuration designer'** and add **'Enable Network Protection in Microsoft Defender'** as the key and value as **'1'** to enable Network Protection. (Network protection is disabled by default)
 
-    > [!div class="mx-imgBorder"]
-    > ![Image of how to select enable network protection policy](media/selectnp.png)
-
-    > [!div class="mx-imgBorder"]
-    > ![Image of add configuration policy.](media/npvalue.png)
-
+      > [!div class="mx-imgBorder"]
+   > ![Screenshot of how to select enable network protection policy](media/selectnp.png)
+   
+      > [!div class="mx-imgBorder"]
+   > ![Screenshot of add configuration policy.](media/npvalue.png)
+   
 1. If your organization uses root CAs that are private, you must establish explicit trust between Intune (MDM solution) and user devices. Establishing trust helps prevent Defender from flagging root CAs as rogue certificates.
 
     To establish trust for the root CAs, use **'Trusted CA certificate list for Network Protection'** as the key. In the value, add the **'comma separated list of certificate thumbprints (SHA 1)'**.
 
     **Example of Thumbprint format to add**: `50 30 06 09 1d 97 d4 f5 ae 39 f7 cb e7 92 7d 7d 65 2d 34 31, 503006091d97d4f5ae39f7cbe7927d7d652d3431`
 
-   > [!IMPORTANT]
+      > [!IMPORTANT]
    > Certificate SHA-1 Thumbprint characters should be with either white space separated, or non separated.
    >
    > This format is invalid: `50:30:06:09:1d:97:d4:f5:ae:39:f7:cb:e7:92:7d:7d:65:2d:34:31`
 
-   Any other separation characters are invalid.
-
-   > ![Image of trusted CA certificate.](media/trustca.png)
+      Any other separation characters are invalid.
 
 1. For other configurations related to Network protection, add the following keys and appropriate corresponding value.
 
@@ -119,26 +115,6 @@ Network protection in Microsoft Defender for endpoint is disabled by default. Ad
 
 > [!NOTE]
 > Users need to enable location permission (which is an optional permission); this enables Defender for Endpoint to scan their networks and alert them when there are WIFI-related threats. If the location permission is denied by the user, Defender for Endpoint will only be able to provide limited protection against network threats and will only protect the users from rogue certificates.
-
-## Configure Low Touch Onboarding
-
-Admins can configure Microsoft Defender for Endpoint in low touch onboarding mode. In this scenario, administrators creates a deployment profile and the user is simply required to provide a reduced set of permissions to complete onboarding. 
-
-Android low touch onboarding is disabled by default. Admins can enable it through app configuration policies on Intune by following these steps:
-
-1.	Push the Defender app to target user group by following these [steps](android-intune.md#add-microsoft-defender-for-endpoint-on-android-as-a-managed-google-play-app).
-2.	Push a VPN profile to the user's device by following the instructions [here](android-intune.md#auto-setup-of-always-on-vpn).
-3.	In Apps > Application configuration policies, select Managed Devices.
-4.	Provide a name to uniquely identify the policy. Select 'Android Enterprise' as the Platform, the required Profile type and 'Microsoft Defender: Antivirus' as the targeted app. Click on Next.
-5.	Add runtime permissions. Select Location access (fine)(This permission is not supported for Android 13 and above), POST_NOTIFICATIONS and change the Permission state to 'Auto grant'.
-6.	Under configuration settings, select 'Use Configuration designer' and click on Add.
-7.	Select Low touch onboarding and User UPN. For User UPN, change the Value type to 'Variable' and Configuration value to 'User Principal Name' from the drop down Enable Low touch onboarding by changing the configuration value to 1.
-    >[!div class="mx-imgBorder"]
-    >![Image of low touch onboarding configuration policy.](media/low-touch-user-upn.png)
-
-8.	Assign the policy to the target user group.
-9.	Review and create the policy.
-
 ## Privacy Controls
 
 Following privacy controls are available for configuring the data that is sent by Defender for Endpoint from Android devices:
@@ -347,11 +323,11 @@ Use the following steps to configure the Device tags:
 5. Click Next and assign this policy to targeted devices and users.
 
 
-> [!NOTE] 
+> [!NOTE]
 > The Defender app needs to be opened for tags to be synced with Intune and passed to Security Portal. It may take up to 18 hours for tags to reflect in the portal.
-
 ## Related articles
 
 - [Overview of Microsoft Defender for Endpoint on Android](microsoft-defender-endpoint-android.md)
+
 - [Deploy Microsoft Defender for Endpoint on Android with Microsoft Intune](android-intune.md)
 [!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/api/get-all-recommendations.md

@@ -100,34 +100,36 @@ Here is an example of the response.
     "@odata.context": "https://api.securitycenter.microsoft.com/api/$metadata#Recommendations",
     "value": [
         {
-            "id": "va-_-microsoft-_-windows_10" "va-_-microsoft-_-windows_11",
-            "productName": "windows_10" "Windows_11",
-            "recommendationName": "Update Windows 10" "Update Windows 11",
-            "weaknesses": 397,
+            "id": "va-_-microsoft-_-edge_chromium-based",
+            "productName": "edge_chromium-based",
+            "recommendationName": "Update Microsoft Edge Chromium-based to version 127.0.2651.74",
+            "weaknesses": 762,
             "vendor": "microsoft",
-            "recommendedVersion": "",
+            "recommendedVersion": "127.0.2651.74",
+            "recommendedVendor": "",
+            "recommendedProgram": "",
             "recommendationCategory": "Application",
             "subCategory": "",
             "severityScore": 0,
             "publicExploit": true,
             "activeAlert": false,
             "associatedThreats": [
-                "3098b8ef-23b1-46b3-aed4-499e1928f9ed",
-                "40c189d5-0330-4654-a816-e48c2b7f9c4b",
-                "4b0c9702-9b6c-4ca2-9d02-1556869f56f8",
-                "e8fc2121-3cf3-4dd2-9ea0-87d7e1d2b29d",
-                "94b6e94b-0c1d-4817-ac06-c3b8639be3ab"
+                "71d9120e-7eea-4058-889a-1a60bbf7e312"
             ],
             "remediationType": "Update",
             "status": "Active",
             "configScoreImpact": 0,
-            "exposureImpact": 7.674418604651163,
-            "totalMachineCount": 37,
-            "exposedMachinesCount": 7,
+            "exposureImpact": 1.1744086343876479,
+            "totalMachineCount": 261,
+            "exposedMachinesCount": 193,
             "nonProductivityImpactedAssets": 0,
-            "relatedComponent": "Windows 10" "Windows 11"
+            "relatedComponent": "Edge Chromium-based",
+            "hasUnpatchableCve": false,
+            "tags": [
+            "internetFacing"
+            ],
+            "exposedCriticalDevices": 116
         }
-        ...
      ]
 }
 ```

defender-endpoint/api/get-all-vulnerabilities.md

@@ -94,21 +94,24 @@ Here is an example of the response.
     "@odata.context": "https://api.securitycenter.microsoft.com/api/$metadata#Vulnerabilities",
     "value": [
         {
-            "id": "CVE-2019-0608",
-            "name": "CVE-2019-0608",
-            "description": "A spoofing vulnerability exists when Microsoft Browsers does not properly parse HTTP content. An attacker who successfully exploited this vulnerability could impersonate a user request by crafting HTTP queries. The specially crafted website could either spoof content or serve as a pivot to chain an attack with other vulnerabilities in web services.To exploit the vulnerability, the user must click a specially crafted URL. In an email attack scenario, an attacker could send an email message containing the specially crafted URL to the user in an attempt to convince the user to click it.In a web-based attack scenario, an attacker could host a specially crafted website designed to appear as a legitimate website to the user. However, the attacker would have no way to force the user to visit the specially crafted website. The attacker would have to convince the user to visit the specially crafted website, typically by way of enticement in an email or instant message, and then convince the user to interact with content on the website.The update addresses the vulnerability by correcting how Microsoft Browsers parses HTTP responses.",
-            "severity": "Medium",
-            "cvssV3": 4.3,
+            "id": "CVE-2024-7256",
+            "name": "CVE-2024-7256",
+            "description": "Summary: Google Chrome is vulnerable to a security bypass due to insufficient data validation in Dawn. An attacker can exploit this vulnerability by tricking a user into visiting a malicious website, allowing them to bypass security restrictions. Impact: If successfully exploited, this vulnerability could allow a remote attacker to bypass security restrictions in Google Chrome. Remediation: Apply the latest patches and updates provided by the respective vendors. Generated by AI",
+            "severity": "High",
+            "cvssV3": 8,
             "cvssVector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C",
-            "exposedMachines": 4,
-            "publishedOn": "2019-10-08T00:00:00Z",
-            "updatedOn": "2019-12-16T16:20:00Z",
+            "exposedMachines": 23,
+            "publishedOn": "2024-07-30T00:00:00Z",
+            "updatedOn": "2024-07-31T00:00:00Z",
+            "firstDetected": "2024-07-31T01:55:47Z",
             "publicExploit": false,
             "exploitVerified": false,
             "exploitInKit": false,
             "exploitTypes": [],
             "exploitUris": [],
-            "CveSupportability": "supported"  
+            "cveSupportability": "Supported",
+            "tags": [],
+            "epss": 0.632
         }
     ]
 

defender-endpoint/api/get-recommendation-by-id.md

@@ -102,7 +102,11 @@ Here's an example of the response.
     "totalMachineCount": 6,
     "exposedMachinesCount": 5,
     "nonProductivityImpactedAssets": 0,
-    "relatedComponent": "Chrome"
+    "relatedComponent": "Chrome",
+    "tags": [
+    "internetFacing"
+    ],
+    "exposedCriticalDevices": 116
 }
 ```
 

defender-endpoint/api/recommendation.md

@@ -80,5 +80,7 @@ Want to experience Defender for Endpoint? [Sign up for a free trial.](https://si
 |exposedMachinesCount|Long|Number of installed devices that are exposed to vulnerabilities|
 |nonProductivityImpactedAssets|Long|Number of devices that aren't affected|
 |relatedComponent|String|Related software component|
-|
+|exposedCriticalDevices|Numeric|The sum of critical devices in all levels of criticality except “not critical" for a particular recommendation|
+
+
 [!INCLUDE [Microsoft Defender for Endpoint Tech Community](../../includes/defender-mde-techcommunity.md)]

defender-endpoint/api/vulnerability.md

@@ -64,5 +64,7 @@ exploitInKit|Boolean|Exploit is part of an exploit kit
 exploitTypes|String collection|Exploit affect. Possible values are: **Local privilege escalation**, **Denial of service**, or **Local**
 exploitUris|String collection|Exploit source URLs
 CveSupportability| String collection| Possible values are: **Supported**, **Not Supported**, or **SupportedInPremium**
+EPSS|Numeric| Represents the probability that a vulnerability will be exploited. This probability is expressed as a number between 0 and 1 (0%-100%) according to the EPSS model.
+
 
 [!INCLUDE [Microsoft Defender for Endpoint Tech Community](../../includes/defender-mde-techcommunity.md)]

defender-endpoint/edr-detection.md

@@ -15,7 +15,7 @@ ms.custom: admindeeplinkDEFENDER
 ms.topic: conceptual
 ms.subservice: edr
 search.appverid: met150
-ms.date: 08/06/2024
+ms.date: 08/15/2024
 ---
 
 # EDR detection test for verifying device's onboarding and reporting services
@@ -76,7 +76,6 @@ After a few minutes, a detection should be raised in Microsoft Defender XDR.
 
 3. Look at the alert details, machine timeline, and perform your typical investigation steps.
 
-<!---
 ### macOS
 
 1. In your browser, Microsoft Edge for Mac or Safari, download *MDATP MacOS DIY.zip* from [https://aka.ms/mdatpmacosdiy](https://aka.ms/mdatpmacosdiy) and extract.
@@ -129,7 +128,6 @@ After a few minutes, a detection should be raised in Microsoft Defender XDR.
 
     Look at the alert details and the device timeline, and perform the regular investigation steps.
 
---->
 
 ## Next steps
 

defender-endpoint/endpoint-attack-notifications.md

@@ -14,7 +14,7 @@ ms.collection:
 ms.topic: conceptual
 ms.subservice: edr
 search.appverid: met150
-ms.date: 09/23/2022
+ms.date: 08/15/2024
 ---
 
 # Endpoint Attack Notifications
@@ -31,7 +31,7 @@ ms.date: 09/23/2022
 > This covers threat hunting on your Microsoft Defender for Endpoint service. However, if you're interested to explore the service beyond your current license, and proactively hunt threats not just on endpoints but also across Office 365, cloud applications, and identity, refer to [Microsoft Defender Experts for Hunting](/defender-xdr/defender-experts-for-hunting).
 
 > [!NOTE]
-> Customers who signed up for Experts on Demand prior to sunset will have access to Ask Defender Experts until the expiration of their current contract.
+> The intake of new customers to the Endpoint Attack Notifications service is currently on pause. For customers interested in a managed service, sign up the [Defender Experts service request form](https://aka.ms/IWantDefenderExperts).
 
 Endpoint Attack Notifications (previously referred to as Microsoft Threat Experts - Targeted Attack Notification) provides proactive hunting for the most important threats to your network, including human adversary intrusions, hands-on-keyboard attacks, or advanced attacks like cyber-espionage. These notifications show up as a new alert. The managed hunting service includes:
 

defender-endpoint/internet-facing-devices.md

@@ -13,7 +13,7 @@ ms.collection:
 - tier2
 ms.topic: conceptual
 search.appverid: met150
-ms.date: 07/10/2023
+ms.date: 07/31/2024
 ---
 
 # Internet-facing devices
@@ -64,6 +64,10 @@ You can use filters to focus in on internet-facing devices and investigate the r
 
    :::image type="content" source="/defender/media/defender-endpoint/internet-facing-filter.png" alt-text="Screenshot of the internet-facing filter" lightbox="/defender/media/defender-endpoint/internet-facing-filter.png":::
 
+The internet-facing device tag also appears in Microsoft Defender Vulnerability Management. This allows you to filter for internet-facing devices from the [weaknesses](/defender-vulnerability-management/tvm-weaknesses) and the [security recommendations](/defender-vulnerability-management/tvm-security-recommendation) pages in the Microsoft Defender portal. 
+
+   :::image type="content" source="/defender/media/defender-endpoint/internet-facing-weaknesses.png" alt-text="Screenshot of the internet-facing weaknesses" lightbox="/defender/media/defender-endpoint/internet-facing-weaknesses.png":::
+
 > [!NOTE]
 > If no new events for a device occur for 48 hours, the Internet-facing tag is removed and it will no longer be visible in the Microsoft Defender portal.
 

defender-endpoint/linux-exclusions.md

@@ -88,7 +88,53 @@ For antivirus exclusions, when using the * wildcard at the end of the path, it w
 
 ### Using the management console
 
-For more information on how to configure exclusions from Puppet, Ansible, or another management console, see [Set preferences for Defender for Endpoint on Linux](linux-preferences.md).
+To configure exclusions from Puppet, Ansible, or another management console, please refer to the following sample `mdatp_managed.json`.
+```JSON
+{
+   "exclusionSettings":{
+     "exclusions":[
+        {
+           "$type":"excludedPath",
+           "isDirectory":true,
+           "path":"/home/*/git<EXAMPLE DO NOT USE>",
+           "scopes": [
+              "epp"
+           ]
+        },
+        {
+           "$type":"excludedPath",
+           "isDirectory":true,
+           "path":"/run<EXAMPLE DO NOT USE>",
+           "scopes": [
+              "global"
+           ]
+        },
+        {
+           "$type":"excludedPath",
+           "isDirectory":false,
+           "path":"/var/log/system.log<EXAMPLE DO NOT USE><EXCLUDED IN ALL SCENARIOS>",
+           "scopes": [
+              "epp", "global"
+           ]
+        },
+        {
+           "$type":"excludedFileExtension",
+           "extension":".pdf<EXAMPLE DO NOT USE>",
+           "scopes": [
+              "epp"
+           ]
+        },
+        {
+           "$type":"excludedFileName",
+           "name":"/bin/cat<EXAMPLE DO NOT USE><NO SCOPE PROVIDED - GLOBAL CONSIDERED>"
+        }
+     ],
+     "mergePolicy":"admin_only"
+   }
+}
+```
+
+For more information, see [Set preferences for Defender for Endpoint on Linux](linux-preferences.md).
 
 ### Using the command line