You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ATPDocs/alerts-overview.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,6 @@ The following table lists the mapping between alert names, their corresponding u
98
98
|[Suspicious modifications to the AD CS security permissions/settings](persistence-privilege-escalation-alerts.md#suspicious-modifications-to-the-ad-cs-security-permissionssettings--external-id-2435)| 2435 | Medium | Privilege escalation |
|MITRE attack sub-technique |[Domain Account (T1087.002)](https://attack.mitre.org/techniques/T1087/002/), [Domain Groups (T1069.002)](https://attack.mitre.org/techniques/T1069/002/)|
175
175
176
-
## Honeytoken was queried via SAM-R (external ID 2439)
177
-
178
-
**Severity**: Low
179
-
180
-
**Description**:
181
-
182
-
User reconnaissance is used by attackers to map the directory structure and target privileged accounts for later steps in their attack. The Security Account Manager Remote (SAM-R) protocol is one of the methods used to query the directory to perform this type of mapping.
183
-
In this detection, Microsoft Defender for Identity will trigger this alert for any reconnaissance activities against a pre-configured [honeytoken user](entity-tags.md)
Copy file name to clipboardExpand all lines: ATPDocs/remediation-actions.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,8 +39,24 @@ The following Defender for Identity actions can be performed directly on your on
39
39
40
40
-**Reset user password** – This will prompt the user to change their password on the next logon, ensuring that this account can't be used for further impersonation attempts.
41
41
42
+
-**Mark User Compromised** - The user’s risk level is set to High
43
+
44
+
-**Suspend User in Entra ID** - Block new sign-ins and access to cloud resources
45
+
46
+
-**Require User to Sign In Again** - Revoke a user’s active sessions
47
+
42
48
Depending on your Microsoft Entra ID roles, you might see additional Microsoft Entra ID actions, such as requiring users to sign in again and confirming a user as compromised. For more information, see [Remediate risks and unblock users](/entra/id-protection/howto-identity-protection-remediate-unblock).
|Mark User Compromised | - Global Administrator <br> - Security Administrator|
55
+
|Suspend User in Entra ID | - Global Administrator |
56
+
|Require User to Sign In Again | - Global Administrator <br> - Security Administrator <br> - Security Operator|
57
+
| Disable/Enable User in Active Directory | Refer to [Required permissions Defender for Identity in Microsoft Defender XDR](/defender-for-identity/role-groups#required-permissions-defender-for-identity-in-microsoft-defender-xdr)|
58
+
| Force Password Reset in Active Directory | Refer to [Required permissions Defender for Identity in Microsoft Defender XDR](/defender-for-identity/role-groups#required-permissions-defender-for-identity-in-microsoft-defender-xdr)|
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -751,10 +751,12 @@ The effect of **No access** permissions (admin only access) on user capabilities
751
751
-**In quarantine notifications**: Users receive quarantine notifications, but the only available action is **Review message**.
752
752
753
753
> [!TIP]
754
-
> To enable quarantine notifications while maintaining restricted access, [create a custom quarantine policy](#step-1-create-quarantine-policies-in-the-microsoft-defender-portal) with the following settings:
755
754
>
756
-
> -**Recipient message access** page: Select **Set specific access (Advanced)**, but leave **Select release action preference** and **Select additional actions recipients can take on quarantined messages** blank/unselected (equivalent to the value 0 for the _EndUserQuarantinePermissionsValue_ parameter on the **New-QuarantinePolicy** cmdlet [in Powershell](#create-quarantine-policies-in-powershell)).
757
-
> -**Quarantine notification** page: Select **Enable** and then select **Don't include quarantined messages from blocked sender addresses** (default) or **Include quarantined messages from blocked sender addresses**.
755
+
> - To enable quarantine notifications while maintaining restricted access, [create a custom quarantine policy](#step-1-create-quarantine-policies-in-the-microsoft-defender-portal) with the following settings:
756
+
> -**Recipient message access** page: Select **Set specific access (Advanced)**, but leave **Select release action preference** and **Select additional actions recipients can take on quarantined messages** blank/unselected (equivalent to the value 0 for the _EndUserQuarantinePermissionsValue_ parameter on the **New-QuarantinePolicy** cmdlet [in Powershell](#create-quarantine-policies-in-powershell)).
757
+
> -**Quarantine notification** page: Select **Enable** and then select **Don't include quarantined messages from blocked sender addresses** (default) or **Include quarantined messages from blocked sender addresses**.
758
+
>
759
+
> - If a sender is blocked and **Don't show blocked senders** is selected (default), messages from those senders are shown on the **Quarantine** page and are included in quarantine notifications when the **Sender address override reason** value is **None**. This behavior occurs because the messages were blocked due to reasons other than sender address overrides.
Copy file name to clipboardExpand all lines: defender-office-365/tenant-allow-block-list-email-spoof-configure.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,14 +47,19 @@ This article describes how admins can manage entries for email senders in the Mi
47
47
48
48
- For blocking inbound and outbound email from a domain, any subdomains in that domain, and any email addresses in that domain, create the block entry using the syntax: `*.TLD`, where `TLD` can be any top-level domain, internal domain, or email address domain.
49
49
50
-
- For blocking inbound and outbound email from a sudomain in a domain and any email addresses in that subdomain, create the block entry using the syntax: `*.SD1.TLD`, `*.SD2.SD1.TLD`, `*.SD3.SD2.SD1.TLD`, etc. for internal domains and email address domains.
50
+
- For blocking inbound and outbound email from a subdomain in a domain and any email addresses in that subdomain, create the block entry using the syntax: `*.SD1.TLD`, `*.SD2.SD1.TLD`, `*.SD3.SD2.SD1.TLD`, etc. for internal domains and email address domains.
51
51
52
52
- For details about the syntax for spoofed sender entries, see the [Domain pair syntax for spoofed sender entries](#domain-pair-syntax-for-spoofed-sender-entries) section later in this article.
53
53
54
54
- An entry should be active within 5 minutes.
55
55
56
56
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
57
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Detection tuning (manage)** or **Authorization and settings/Security settings/Core security settings (read)**.
57
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
58
+
-*Add and remove entries from the Tenant Allow/Block List*: Membership assigned with the following permissions:
59
+
-**Authorization and settings/Security settings/Detection tuning (manage)**
60
+
-*Read-only access to the Tenant Allow/Block List*:
61
+
-**Authorization and settings/Security settings/Read-only**.
62
+
-**Authorization and settings/Security settings/Core Security settings (read)**.
Copy file name to clipboardExpand all lines: defender-office-365/tenant-allow-block-list-files-configure.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,12 @@ This article describes how admins can manage entries for files in the Microsoft
54
54
- An entry should be active within 5 minutes.
55
55
56
56
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
57
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Exchange Online permissions** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Detection tuning (manage)** or **Authorization and settings/Security settings/Core security settings (read)**.
57
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
58
+
-*Add and remove entries from the Tenant Allow/Block List*: Membership assigned with the following permissions:
59
+
-**Authorization and settings/Security settings/Detection tuning (manage)**
60
+
-*Read-only access to the Tenant Allow/Block List*:
61
+
-**Authorization and settings/Security settings/Read-only**.
62
+
-**Authorization and settings/Security settings/Core Security settings (read)**.
Copy file name to clipboardExpand all lines: defender-office-365/tenant-allow-block-list-ip-addresses-configure.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,12 @@ This article describes how admins can manage entries for IPv6 addresses in the M
52
52
- An entry should be active within 5 minutes.
53
53
54
54
- You need to be assigned permissions before you can do the procedures in this article. You have the following options:
55
-
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Exchange Online permissions** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell): **Authorization and settings/Security settings/Detection tuning (manage)** or **Authorization and settings/Security settings/Core security settings (read)**.
55
+
-[Microsoft Defender XDR Unified role based access control (RBAC)](/defender-xdr/manage-rbac) (If **Email & collaboration**\>**Defender for Office 365** permissions is :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **Active**. Affects the Defender portal only, not PowerShell):
56
+
-*Add and remove entries from the Tenant Allow/Block List*: Membership assigned with the following permissions:
57
+
-**Authorization and settings/Security settings/Detection tuning (manage)**
58
+
-*Read-only access to the Tenant Allow/Block List*:
59
+
-**Authorization and settings/Security settings/Read-only**.
60
+
-**Authorization and settings/Security settings/Core Security settings (read)**.
0 commit comments