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: defender-endpoint/attack-surface-reduction-rules-reference.md
+20-16Lines changed: 20 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,8 @@ ms.service: defender-endpoint
5
5
ms.subservice: asr
6
6
ms.localizationpriority: medium
7
7
audience: ITPro
8
-
author: denisebmsft
9
-
ms.author: deniseb
8
+
author: emmwalshh
9
+
ms.author: ewalsh
10
10
ms.reviewer: sugamar, yongrhee
11
11
manager: deniseb
12
12
ms.custom: asr
@@ -15,7 +15,7 @@ ms.collection:
15
15
- m365-security
16
16
- tier2
17
17
- mde-asr
18
-
ms.date: 03/05/2025
18
+
ms.date: 04/02/2025
19
19
search.appverid: met150
20
20
---
21
21
@@ -179,7 +179,7 @@ Toast notifications are generated for all rules in Block mode. Rules in any othe
179
179
For rules with the "Rule State" specified:
180
180
181
181
- ASR rules with `\ASR Rule, Rule State\` combinations are used to surface alerts (toast notifications) on Microsoft Defender for Endpoint only for devices set at the cloud block level `High`.
182
-
- Devices that are not set at the cloud block level `High` don't generate alerts for any `ASR Rule, Rule State` combinations.
182
+
- Devices that aren't set at the cloud block level `High` don't generate alerts for any `ASR Rule, Rule State` combinations.
183
183
- EDR alerts are generated for ASR rules in the specified states, for devices set at the cloud block level `High+`.
184
184
- Toast notifications occur in block mode only and for devices set at the cloud block level `High`.
185
185
@@ -326,22 +326,22 @@ This rule helps prevent credential stealing by locking down Local Security Autho
326
326
327
327
LSASS authenticates users who sign in on a Windows computer. Microsoft Defender Credential Guard in Windows normally prevents attempts to extract credentials from LSASS. Some organizations can't enable Credential Guard on all of their computers because of compatibility issues with custom smartcard drivers or other programs that load into the Local Security Authority (LSA). In these cases, attackers can use tools like Mimikatz to scrape cleartext passwords and NTLM hashes from LSASS.
328
328
329
-
By default the state of this rule is set to block. In most cases, many processes make calls to LSASS for access rights that are not needed. For example, such as when the initial block from the ASR rule results in a subsequent call for a lesser privilege which subsequently succeeds. For information about the types of rights that are typically requested in process calls to LSASS, see [Process Security and Access Rights](/windows/win32/procthread/process-security-and-access-rights).
329
+
By default the state of this rule is set to block. In most cases, many processes make calls to LSASS for access rights that aren't needed. For example, such as when the initial block from the ASR rule results in a subsequent call for a lesser privilege which then succeeds. For information about the types of rights that are typically requested in process calls to LSASS, see [Process Security and Access Rights](/windows/win32/procthread/process-security-and-access-rights).
330
330
331
-
Enabling this rule doesn't provide additional protection if you have LSA protection enabled since the ASR rule and LSA protection work similarly. However, when LSA protection cannot be enabled, this rule can be configured to provide equivalent protection against malware that target `lsass.exe`.
331
+
Enabling this rule doesn't provide additional protection if you have LSA protection enabled since the ASR rule and LSA protection work similarly. However, when LSA protection can't be enabled, this rule can be configured to provide equivalent protection against malware that target `lsass.exe`.
332
332
333
333
> [!TIP]
334
334
>
335
335
> 1. ASR audit events don't generate toast notifications. However, since the LSASS ASR rule produces large volume of audit events, almost all of which are safe to ignore when the rule is enabled in block mode, you can choose to skip the audit mode evaluation and proceed to block mode deployment, beginning with a small set of devices and gradually expanding to cover the rest.
336
-
> 2. The rule is designed to suppress block reports/toasts for friendly processes. It is also designed to drop reports for duplicate blocks. As such, the rule is well suited to be enabled in block mode, irrespective of whether toast notifications are enabled or disabled.
336
+
> 2. The rule is designed to suppress block reports/toasts for friendly processes. It's also designed to drop reports for duplicate blocks. As such, the rule is well suited to be enabled in block mode, irrespective of whether toast notifications are enabled or disabled.
337
337
> 3. ASR in warn mode is designed to present users with a block toast notification that includes an "Unblock" button. Due to the "safe to ignore" nature of LSASS ASR blocks and their large volume, WARN mode isn't advisable for this rule (irrespective of whether toast notifications are enabled or disabled).
338
338
339
339
> [!NOTE]
340
340
> In this scenario, the ASR rule is classified as "not applicable" in Defender for Endpoint settings in the Microsoft Defender portal.
341
341
>
342
342
> The *Block credential stealing from the Windows local security authority subsystem* ASR rule doesn't support WARN mode.
343
343
>
344
-
> In some apps, the code enumerates all running processes and attempts to open them with exhaustive permissions. This rule denies the app's process open action and logs the details to the security event log. This rule can generate a lot of noise. If you have an app that simply enumerates LSASS, but has no real impact in functionality, there's no need to add it to the exclusion list. By itself, this event log entry doesn't necessarily indicate a malicious threat.
344
+
> In some apps, the code enumerates all running processes and attempts to open them with exhaustive permissions. This rule denies the app's process open action and logs the details to the security event log. This rule can generate numerous noise. If you have an app that simply enumerates LSASS, but has no real impact in functionality, there's no need to add it to the exclusion list. By itself, this event log entry doesn't necessarily indicate a malicious threat.
345
345
Intune name: `Flag credential stealing from the Windows local security authority subsystem`
346
346
347
347
Configuration Manager name: `Block credential stealing from the Windows local security authority subsystem`
@@ -370,6 +370,8 @@ This rule blocks email opened within the Microsoft Outlook application, or Outlo
370
370
- Executable files (such as .exe, .dll, or .scr)
371
371
- Script files (such as a PowerShell .ps1, Visual Basic .vbs, or JavaScript .js file)
372
372
373
+
- Archive files (such as .zip and others)
374
+
373
375
Intune name: `Execution of executable content (exe, dll, ps, js, vbs, etc.) dropped from email (webmail/mail client) (no exceptions)`
374
376
375
377
Microsoft Configuration Manager name: `Block executable content from email client and webmail`
@@ -435,7 +437,7 @@ Advanced hunting action type:
435
437
-`AsrObfuscatedScriptAudited`
436
438
-`AsrObfuscatedScriptBlocked`
437
439
438
-
Dependencies: Microsoft Defender Antivirus, AntiMalware Scan Interface (AMSI), Cloud Protection
440
+
Dependencies: Microsoft Defender Antivirus, Anti-malware Scan Interface (AMSI), Cloud Protection
439
441
440
442
### Block JavaScript or VBScript from launching downloaded executable content
441
443
@@ -456,7 +458,7 @@ Dependencies: Microsoft Defender Antivirus, AMSI
456
458
457
459
### Block Office applications from creating executable content
458
460
459
-
This rule prevents Office apps, including Word, Excel, and PowerPoint, from creating potentially malicious executable content, by blocking malicious code from being written to disk. Malware that abuses Office as a vector might attempt to break out of Office and save malicious components to disk. These malicious components would survive a computer reboot and persist on the system. Therefore, this rule defends against a common persistence technique. This rule also blocks execution of untrusted files that may have been saved by Office macros that are allowed to run in Office files.
461
+
This rule prevents Office apps, including Word, Excel, and PowerPoint, from creating potentially malicious executable content, by blocking malicious code from being written to disk. Malware that abuses Office as a vector might attempt to break out of Office and save malicious components to disk. These malicious components would survive a computer reboot and persist on the system. Therefore, this rule defends against a common persistence technique. This rule also blocks execution of untrusted files that might have been saved by Office macros that are allowed to run in Office files.
@@ -476,7 +478,7 @@ Dependencies: Microsoft Defender Antivirus, RPC
476
478
This rule blocks code injection attempts from Office apps into other processes.
477
479
478
480
> [!NOTE]
479
-
> The Block applications from injecting code into other processes ASR rule doesn't support WARN mode.
481
+
> The Block applications from injecting code into other processes ASR rule don't support WARN mode.
480
482
481
483
> [!IMPORTANT]
482
484
> This rule requires restarting Microsoft 365 Apps (Office applications) for the configuration changes to take effect.
@@ -574,7 +576,7 @@ Dependencies: Microsoft Defender Antivirus
574
576
This rule prevents the execution of commands to restart machines in Safe Mode. Safe Mode is a diagnostic mode that only loads the essential files and drivers needed for Windows to run. However, in Safe Mode, many security products are either disabled or operate in a limited capacity, which allows attackers to further launch tampering commands, or execute and encrypt all files on the machine. This rule blocks such attacks by preventing processes from restarting machines in Safe Mode.
575
577
576
578
> [!NOTE]
577
-
> This capability is currently in preview. Additional upgrades to improve efficacy are under development.
579
+
> This capability is currently in preview. Extra upgrades to improve efficacy are under development.
578
580
579
581
Intune Name: `[PREVIEW] Block rebooting machine in Safe Mode`
580
582
@@ -595,7 +597,7 @@ Dependencies: Microsoft Defender Antivirus
595
597
With this rule, admins can prevent unsigned or untrusted executable files from running from USB removable drives, including SD cards. Blocked file types include executable files (such as .exe, .dll, or .scr)
596
598
597
599
> [!IMPORTANT]
598
-
> Files copied from the USB to the disk drive will be blocked by this rule if and when it's about to be executed on the disk drive.
600
+
> Files copied from the USB to the disk drive are blocked by this rule if and when it's about to be executed on the disk drive.
599
601
600
602
Intune name: `Untrusted and unsigned processes that run from USB`
601
603
@@ -612,7 +614,7 @@ Dependencies: Microsoft Defender Antivirus
612
614
613
615
### Block use of copied or impersonated system tools (preview)
614
616
615
-
This rule blocks the use of executable files that are identified as copies of Windows system tools. These files are either duplicates or impostors of the original system tools. Some malicious programs may try to copy or impersonate Windows system tools to avoid detection or gain privileges. Allowing such executable files can lead to potential attacks. This rule prevents propagation and execution of such duplicates and impostors of the system tools on Windows machines.
617
+
This rule blocks the use of executable files that are identified as copies of Windows system tools. These files are either duplicates or impostors of the original system tools. Some malicious programs might try to copy or impersonate Windows system tools to avoid detection or gain privileges. Allowing such executable files can lead to potential attacks. This rule prevents propagation and execution of such duplicates and impostors of the system tools on Windows machines.
616
618
617
619
> [!NOTE]
618
620
> This capability is currently in preview. Additional upgrades to improve efficacy are under development.
@@ -635,7 +637,9 @@ Dependencies: Microsoft Defender Antivirus
635
637
636
638
### Block Webshell creation for Servers
637
639
638
-
This rule blocks web shell script creation on Microsoft Server, Exchange Role. A web shell script is a specifically crafted script that allows an attacker to control the compromised server. A web shell may include functionalities such as receiving and executing malicious commands, downloading and executing malicious files, stealing and exfiltrating credentials and sensitive information, and identifying potential targets.
640
+
This rule blocks web shell script creation on Microsoft Server, Exchange Role. A web shell script is a crafted script that allows an attacker to control the compromised server.
641
+
642
+
A web shell might include functionalities such as receiving and executing malicious commands, downloading and executing malicious files, stealing and exfiltrating credentials and sensitive information, and identifying potential targets.
639
643
640
644
Intune name: `Block Webshell creation for Servers`
641
645
@@ -664,7 +668,7 @@ Dependencies: Microsoft Defender Antivirus, AMSI
664
668
665
669
This rule provides an extra layer of protection against ransomware. It uses both client and cloud heuristics to determine whether a file resembles ransomware. This rule doesn't block files that have one or more of the following characteristics:
666
670
667
-
- The file has already been found to be unharmful in the Microsoft cloud.
671
+
- The file is found to be unharmful in the Microsoft cloud.
668
672
- The file is a valid signed file.
669
673
- The file is prevalent enough to not be considered as ransomware.
title: OAuthAppInfo table in the advanced hunting schema
3
+
description: Learn about the OAuthAppInfo table which contains information about Microsoft 365-connected OAuth applications registered with Microsoft Entra ID and available in the Defender for Cloud Apps app governance capability.
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
32
+
33
+
The `OAuthAppInfo` table in the advanced hunting schema contains information about Microsoft 365-connected OAuth applications in the organization that are registered with Microsoft Entra ID and available in the Microsoft Defender for Cloud Apps app governance capability.
34
+
35
+
The `OAuthAppInfo` table might not include all the app or service principal-related properties that are available on Entra ID. It also does not include data related to Microsoft first-party apps or apps without any OAuth consents. The coverage of the table is based on the existing scope of Microsoft 365-connected apps covered by app governance.
36
+
37
+
38
+
For information on other tables in the advanced hunting schema, see [the advanced hunting reference](advanced-hunting-schema-tables.md).
39
+
40
+
| Column name | Data type | Description |
41
+
|-------------|-----------|-------------|
42
+
|`ReportId`|`string`| Unique identifier for the record|
43
+
|`Timestamp`|`string`| Date and time when the record was created|
44
+
|`OAuthAppId`|`string`| The unique identifier for the app as assigned by Microsoft Entra ID|
45
+
|`ServicePrincipalId`|`string`| The unique identifier for the service principal instance of the application in the tenant|
46
+
|`AppName`|`string`| The application's display name as exposed by the associated service principal|
47
+
|`AddedOnTime`|`datetime`| Date and time when the application was registered|
48
+
|`LastModifiedTime`|`datetime`| Timestamp when the app was last modified|
49
+
|`AppStatus`|`string`| Status of the app; can be: Enabled, DisabledByMicrosoft, DisabledByAppGovernancePolicy, DisabledByUser, Deleted (information for apps with Deleted status is only available for 30 days since the app was deleted)|
50
+
|`VerifiedPublisher`|`dynamic`| Specifies details about the verified publisher of the application which this service principal represents. It includes information such as: DisplayName, VerifiedPublisherId, AddedDateTime|
51
+
|`PrivilegeLevel`|`string`| The privilege level of the app based on the highest classified permission granted to the app|
52
+
|`Permissions`|`dynamic`| Contains an array of permission objects; each permission object includes PermissionName, TargetAppId, TargetAppDisplayName, PermissionType, PrivilegeLevel, UsageStatus|
53
+
|`ConsentedUsersCount`|`integer`| Count of users who have consented to the app; this information is only available when the app is not admin consented|
54
+
|`IsAdminConsented`|`boolean`| Value is True if a user has provided admin consent to the app on behalf of all the users in the org, otherwise the value is False|
55
+
|`AppOrigin`|`string`| Specifies whether the app is internal to the organization or registered in an external tenant|
56
+
|`LastUsedTime`|`datetime`| Date and time when the app was last used|
57
+
|`AppOwnerTenantId`|`string`|Specifies the ID of the tenant where the app was registered|
58
+
59
+
60
+
The `OAuthAppInfo` table updates information on an hourly basis to record any changes in metadata or insights for OAuth apps based on data from Defender for Cloud Apps app governance.
61
+
62
+
Additionally, to ensure that `OAuthAppInfo` table retains data for the covered apps, a complete snapshot of all OAuth apps is sent twice a month.
63
+
64
+
65
+
66
+
67
+
## Related topics
68
+
69
+
-[Proactively hunt for threats](advanced-hunting-overview.md)
70
+
-[Learn the query language](advanced-hunting-query-language.md)
71
+
-[Understand the schema](advanced-hunting-schema-tables.md)
72
+
-[Apply query best practices](advanced-hunting-best-practices.md)
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-schema-tables.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,7 @@ The following reference lists all the tables in the schema. Each table name link
100
100
|**[IdentityInfo](advanced-hunting-identityinfo-table.md)**| Account information from various sources, including Microsoft Entra ID |
101
101
|**[IdentityLogonEvents](advanced-hunting-identitylogonevents-table.md)**| Authentication events on Active Directory and Microsoft online services |
102
102
|**[IdentityQueryEvents](advanced-hunting-identityqueryevents-table.md)**| Queries for Active Directory objects, such as users, groups, devices, and domains |
103
+
|**[OAuthAppInfo](advanced-hunting-oauthappinfo-table.md)** (Preview) | Microsoft 365-connected OAuth applications registered with Microsoft Entra ID and available in the Defender for Cloud Apps app governance capability |
103
104
|**[UrlClickEvents](advanced-hunting-urlclickevents-table.md)**| Safe Links clicks from email messages, Teams, and Office 365 apps |
Copy file name to clipboardExpand all lines: defender-xdr/whats-new.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,9 @@ For more information on what's new with other Microsoft Defender security produc
32
32
33
33
You can also get product updates and important notifications through the [message center](https://admin.microsoft.com/Adminportal/Home#/MessageCenter).
34
34
35
+
36
+
## April 2025
37
+
- (Preview) The [OAuthAppInfo](advanced-hunting-oauthappinfo-table.md) table is now available for preview in advanced hunting. The table contains information about Microsoft 365-connected OAuth applications registered with Microsoft Entra ID and available in the Defender for Cloud Apps app governance capability.
35
38
## March 2025
36
39
37
40
- (Preview) The incident description has moved within the incident page. The incident description is now displayed after the incident details. For more information, see [Incident details](investigate-incidents.md#incident-details).
0 commit comments