Skip to content

Commit b294f14

Browse files
authored
Merge branch 'public' into patch-2
2 parents 3f1d830 + 5bff6e3 commit b294f14

File tree

277 files changed

+2163
-2147
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

277 files changed

+2163
-2147
lines changed

.openpublishing.redirection.defender-endpoint.json

Lines changed: 28 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",
@@ -94,6 +94,31 @@
9494
"source_path": "defender-endpoint/monthly-security-summary-report.md",
9595
"redirect_url": "/defender-endpoint/threat-protection-reports#monthly-security-summary",
9696
"redirect_document_id": true
97-
}
97+
},
98+
{
99+
"source_path": "defender-endpoint/run-analyzer-macos-linux.md",
100+
"redirect_url": "/defender-endpoint/overview-client-analyzer",
101+
"redirect_document_id": true
102+
},
103+
{
104+
"source_path": "defender-endpoint/download-client-analyzer.md",
105+
"redirect_url": "/defender-endpoint/overview-client-analyzer",
106+
"redirect_document_id": false
107+
},
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+
},
113+
{
114+
"source_path": "defender-endpoint/comprehensive-guidance-on-linux-deployment.md",
115+
"redirect_url": "/defender-endpoint/linux-installer-script",
116+
"redirect_document_id": true
117+
},
118+
{
119+
"source_path": "defender-endpoint/linux-schedule-scan-mde.md",
120+
"redirect_url": "/defender-endpoint/schedule-antivirus-scan-crontab",
121+
"redirect_document_id": true
122+
}
98123
]
99124
}
70 KB
Loading
76.2 KB
Loading

ATPDocs/remove-rbcd-microsoft-entra-seamless-single-sign-on-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: 'Security assessment: Remove Resource Based Constrained Delegation for Microsoft Entra seamless SSO account'
33
description: This article describes Microsoft Defender for Identity's Microsoft Entra Seamless Single sign-on (SSO) account with Resource Based Constrained Delegation (RBCD) applied security posture assessment report.
44
author: RonitLitinsky
5-
ms.author: t-rlitinsky
5+
ms.author: rlitinsky
66
ms.service: microsoft-defender-for-identity
77
ms.topic: article
88
ms.date: 08/22/2024
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
# Required metadata
3+
# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
4+
# For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
5+
6+
title: 'Security assessment: Remove unsafe permissions on sensitive Microsoft Entra Connect accounts'
7+
description: This report lists any sensitive AD DS Connector (MSOL_) accounts or Microsoft Entra Seamless SSO computer account (AZUREADSSOACC) with unsafe permissions.
8+
author: LiorShapiraa # GitHub alias
9+
ms.author: liorshapira
10+
ms.service: microsoft-defender-for-identity
11+
ms.topic: article
12+
ms.date: 03/16/2025
13+
---
14+
15+
# Security assessment: Remove unsafe permissions on sensitive Entra Connect accounts
16+
17+
This article describes Microsoft Defender for Identity's Microsoft Entra Connect accounts unsafe permissions security posture assessment report.
18+
19+
> [!NOTE]
20+
> This security assessment will be available only if Microsoft Defender for Identity sensor is installed on servers running Microsoft Entra Connect services and Sign on method as part of Microsoft Entra Connect configuration is set to single sign-on and the SSO computer account exists. Learn more about Microsoft Entra seamless sign-on **[here](/entra/identity/hybrid/connect/how-to-connect-sso)**.
21+
22+
## How can unsafe permissions on Microsoft Entra Connect accounts expose your hybrid identity to risk?
23+
24+
Microsoft Entra Connect accounts like AD DS Connector account (also known as MSOL_) and Microsoft Entra Seamless SSO computer account (AZUREADSSOACC) have powerful privileges, including replication and password reset rights. If these accounts are granted unsafe permissions, attackers could exploit them to gain unauthorized access, escalate privileges, or take control of hybrid identity infrastructure. This could lead to account takeovers, unauthorized directory modifications, and a broader compromise of both on-premises and cloud environments.
25+
26+
## How do I use this security assessment to improve my hybrid organizational security posture?
27+
28+
> [!NOTE]
29+
> While assessments are updated in near real time, scores and statuses are updated every 24 hours. While the list of impacted entities is updated within a few minutes of your implementing the recommendations, the status may still take time until it's marked as **Completed**.
30+
31+
1. Review the recommended action at[ https://security.microsoft.com/securescore?viewid=actions](https://security.microsoft.com/securescore?viewid=actions) for Remove unsafe permissions on sensitive Entra Connect accounts.
32+
33+
1. Review the list of exposed entities to identify accounts with unsafe permissions. For example:
34+
35+
:::image type="content" source="media/remove-unsafe-permissions-sensitive-entra-connect/screenshot-of-exposed-entities.png" alt-text="Screenshot of exposed entities" lightbox="media/remove-unsafe-permissions-sensitive-entra-connect/screenshot-of-exposed-entities.png":::
36+
37+
1. If you click on "Click to expend" you can find more details about the granted permissions. For example:
38+
39+
:::image type="content" source="media/remove-unsafe-permissions-sensitive-entra-connect/screenshot-of-excessive-permissions.png" alt-text="Screenshot of excessive permissions" lightbox="media/remove-unsafe-permissions-sensitive-entra-connect/screenshot-of-excessive-permissions.png":::
40+
41+
1. For each exposed account, remove problematic permissions that allow unprivileged accounts to takeover critical hybrid assets.
42+
43+
44+
## Next steps
45+
46+
- [Learn more about Microsoft Secure Score](/microsoft-365/security/defender/microsoft-secure-score)
47+
48+
- [Learn more about Defender for Identity Sensor for Microsoft Entra Connect](https://aka.ms/MdiSensorForMicrosoftEntraConnectInstallation)
49+

ATPDocs/toc.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,9 @@ items:
172172
displayName: Microsoft Entra Connect
173173
- name: Remove unnecessary replication permissions for Microsoft Entra Connect connector account
174174
href: remove-replication-permissions-microsoft-entra-connect.md
175+
- name: Remove unsafe permissions on sensitive Entra Connect accounts
176+
href: remove-unsafe-permissions-sensitive-entra-connect.md
177+
displayName: MDI
175178
- name: Replace Enterprise or Domain Admin account for Entra Connect AD DS Connector account
176179
href: replace-entra-connect-default-admin.md
177180
- name: Identity infrastructure

CloudAppSecurityDocs/accounts.md

Lines changed: 39 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -8,63 +8,62 @@ ms.topic: how-to
88

99

1010

11-
Microsoft Defender for Cloud Apps gives you visibility into the accounts from your connected apps. After you connect Defender for Cloud Apps to an app using the App connector, Defender for Cloud Apps reads account information associated with connected apps. The Accounts page enables you to investigate those accounts, permissions, the groups they're members of, their aliases, and the apps they're using. Additionally, when Defender for Cloud Apps detects a new account that wasn't previously seen in one of the connected apps - for example, in activities or file sharing - the account is added to the accounts list of that app. This enables you to have visibility into the activity of external users interacting with your cloud apps.
11+
Microsoft Defender for Cloud Apps gives you visibility into the accounts from your connected applications. After you connect Defender for Cloud Apps to an app using the [App connector](/defender-cloud-apps/enable-instant-visibility-protection-and-governance-actions-for-your-apps), Defender for Cloud Apps reads account information associated with connected applications. The Cloud application accounts tab within the Identity inventory enables you to investigate those accounts, permissions, the groups they're members of, their aliases, and the apps they're using. Additionally, when Defender for Cloud Apps detects a new account that wasn't previously seen in one of the connected apps - for example, in activities or file sharing - the account is added to the accounts list of that app. This enables you to have visibility into the activity of external users interacting with your cloud apps.
1212

13-
## Identity Inventory (Preview)
13+
## Identity Inventory
1414

15-
> [!NOTE]
16-
> The Identities page is in the process of merging into the unified **Identity Inventory (Preview)**.
17-
>
18-
> The **Identity inventory** provides a centralized view of all identities in your organization, enabling you to monitor and manage them efficiently. At a glance, you can see key details such as Domain, Tags, Type, and other attributes, helping you quickly identify and manage identities that require attention.
19-
>
20-
> The functionality of the Identities page, as presented below, will be provided in the new Identity Inventory under the "**Cloud application accounts**" tab, offering the same features as it does today. For more details, visit the [Identity Inventory documentation](/defender-for-identity/identity-inventory).
21-
>
22-
## Identities
15+
The visibility into cloud application accounts, as described above, is provided in the Identity Inventory under the "**Cloud application accounts**" tab.
2316

24-
Admins can search for a specific user's metadata or user's activity. The **Identities** page provides you with comprehensive details about the entities that are pulled from connected cloud applications. It also provides the user's activity history and security alerts related to the user.
17+
The **Identity inventory** provides a centralized view of all identities in your organization, enabling you to monitor and manage them efficiently. At a glance, you can see key details such as Domain, Tags, Type, and other attributes, helping you quickly identify and manage identities that require attention.
2518

26-
The **Identities** page can be [filtered](#identities-filters) to enable you to find specific accounts and to deep dive into different types of accounts, for example, you can filter for all External accounts that haven't been accessed since last year.
19+
For more details, visit the [Identity Inventory documentation](/defender-for-identity/identity-inventory).
2720

28-
The **Identities** page enables you to easily investigate your accounts, including the following issues:
21+
## Cloud Application Accounts
2922

30-
* Check if any accounts have been inactive in a particular service for a long time (Maybe you should revoke the license for that user to that service)
23+
Admins can search for specific account metadata or account activity. The **Cloud application accounts** tab provides comprehensive details about entities pulled from connected cloud applications, including activity history and security alerts related to the account.
3124

32-
* You can filter for the list of users with admin permissions
33-
* You can search for users who are no longer part of your organization but may still have active accounts
34-
* You can take [governance actions](#governance-actions) on the accounts, such as suspending an app or going to the account settings page.
35-
* You can see which accounts are included in each user group
36-
* You can see which apps are accessed by each account and which apps are deleted for specific accounts
25+
The **Cloud application accounts** tab can be filtered to find specific accounts and deep dive into different types of accounts. For example, you can filter for all External accounts that haven't been accessed since last year.
3726

38-
![accounts screen.](media/accounts-page.png)
39-
40-
### Identities filters
27+
The **Cloud application accounts** tab enables easy investigation of accounts, including:
28+
29+
- Checking if any accounts have been inactive in a particular service for a long time (consider revoking the license for that user to that service).
30+
31+
- Filtering for accounts with admin permissions.
32+
33+
- Searching for accounts that are no longer part of your organization but may still have active accounts.
34+
35+
- Taking governance actions on accounts, such as suspending an app or accessing the account settings page.
36+
37+
- Viewing which accounts are included in each user group.
38+
39+
- Seeing which apps are accessed by each account and which apps are deleted for specific accounts.
4140

42-
Following is a list of the account filters that can be applied. Most filters support multiple values as well as NOT, in order to provide you with a powerful tool for policy creation.
41+
[![Screenshot that shows the Cloud application accounts](media/accounts/cloud-application-accounts.png)](media/accounts/cloud-application-accounts.png#lightbox)
4342

44-
* **Affiliation**: The affiliation is either **Internal** or **External**. To set which users and accounts are internal, under **Settings** make sure to set the **IP address range** of your internal organization. If the account has admin permissions the icon in the Accounts table appears with the addition of the red tie:
43+
### Accounts filters
44+
45+
The Cloud application accounts tab offers comprehensive filtering capabilities, with pre-defined filters for a quick and easy experience.
46+
47+
Admins can also enable the "Advanced filters" toggle to filter by additional attributes or create complex filters that include conditions such as "does not equal."
48+
![Screenshot that shows the Advanced filters toggle.](media/accounts/image.png)
49+
50+
Predefined filters include:
51+
52+
- **Account name:** Filter specific accounts.
53+
54+
- **Affiliation:** Internal or External. Set internal accounts under **Settings** by defining the **IP address range of your organization**. Admin accounts are marked with a red tie icon.
4555

4656
![accounts admin icon.](media/accounts-admin-icon.png)
4757

48-
* **App**: You can filter for any API connected app being used by accounts in your organization.
49-
* **Domain**: This enables you to filter for users in specific domains.
50-
* **Groups**: Enables you to filter for members of user groups in Defender for Cloud Apps - both built-in user groups and imported user groups.
51-
* **Instance**: This enables you to filter for members of a specific app instance.
52-
* **Last seen**: The **last seen** filter enables you to find accounts that are dormant and whose users haven't performed any activities in a while.
53-
* **Organization**: This enables you to filter for members of specific organizational groups defined in your connected apps.
54-
* **Show Admins only**: Filters for accounts and users that are admins.
55-
* **Status**: Filter based on user account status of N/A, staged, active, suspended, or deleted. A status of not available (N/A) is normal and may appear, for example, for anonymous accounts.
56-
* **Type**: This enables you to filter to either the user or the account type.
57-
* **User name**: Enables you to filter specific users.
58-
59-
### Governance actions
58+
- **App:** Filter for any connected app used by accounts in your organization.
6059

61-
From the **Users and account** page, you can take governance actions such as suspending an app or going to the account settings page. For a full list of governance actions, see the [governance log](governance-actions.md).
60+
- **Groups:** Filter for members of user groups in Defender for Cloud Apps—both built-in and imported user groups.
6261

63-
For example, if you identify a user that is compromised, you can apply the **Confirm user compromised** action to set the user risk level to high, causing the relevant policy actions defined in Microsoft Entra ID to be enforced. The action can be applied manually or using relevant [policies that support governance actions](governance-actions.md).
62+
- **Show Admins only:** Filter for admin accounts.
6463

65-
#### To manually apply a user or account governance action
64+
### Additional actions
6665

67-
From the **Users and account** page, on the row where the relevant user or account appears, choose the three dots at the end of the row, then select **Confirm user compromised**.
66+
Additional actions for further investigation, such as viewing related activities and incidents, are available through the Cloud application accounts tab. Click the three dots at the end of the relevant account's row to view available actions, or click on the account row to see additional accounts related to a single user. Additional actions are also available via the three dots at the end of the table in this view.
6867

6968
## Next steps
7069

CloudAppSecurityDocs/activity-filters-queries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Below is a list of the activity filters that can be applied. Most filters suppor
3535
- Administrative activity – Search only for administrative activities.
3636

3737
>[!NOTE]
38-
> Defender for Cloud Apps can't mark Google Cloud Platform (GCP) administrative activities as administrative activities.
38+
> Defender for Cloud Apps classifies all GCP activities as administrative activities.
3939
4040
- Alert ID - Search by alert ID.
4141

CloudAppSecurityDocs/additional-integrations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,6 @@ The Defender for Cloud Apps robust platform allows you to integrate with a wide
2727

2828
Defender for Cloud Apps allows security teams to automatically or manually confirm a user as compromised to ensure fast remediation of compromised users.
2929

30-
For more information, see [How does Microsoft Entra ID use my risk feedback](/azure/active-directory/identity-protection/howto-identity-protection-risk-feedback#how-does-azure-ad-use-my-risk-feedback) and [Governance actions](accounts.md#governance-actions).
30+
For more information, see [How does Microsoft Entra ID use my risk feedback](/azure/active-directory/identity-protection/howto-identity-protection-risk-feedback#how-does-azure-ad-use-my-risk-feedback).
3131

3232
[!INCLUDE [Open support ticket](includes/support.md)]

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).

0 commit comments

Comments
 (0)