Skip to content

Commit 2add3c0

Browse files
Merge pull request #654 from MicrosoftDocs/main
Publish main to live, 06/10, 3:30 PM IST
2 parents 7c6b276 + 1f2d693 commit 2add3c0

File tree

3 files changed

+104
-26
lines changed

3 files changed

+104
-26
lines changed

defender-endpoint/demonstration-behavior-monitoring.md

Lines changed: 101 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -28,27 +28,102 @@ ms.date: 05/15/2024
2828
- [Microsoft Defender Antivirus](microsoft-defender-antivirus-windows.md)
2929
- [Microsoft Defender for Individuals](https://www.microsoft.com/microsoft-365/microsoft-defender-for-individuals)
3030

31-
Behavior Monitoring in Microsoft Defender Antivirus monitors process behavior to detect and analyze potential threats based on the behavior of applications, services, and files. Rather than relying solely on content matching, which identifies known malware patterns, behavior monitoring focuses on observing how software behaves in real-time.
31+
Behavior monitoring in Microsoft Defender Antivirus monitors process behavior to detect and analyze potential threats based on the behavior of applications, services, and files. Rather than relying solely on content matching, which identifies known malware patterns, behavior monitoring focuses on observing how software behaves in real-time.
3232

3333
## Scenario requirements and setup
3434

35-
- This demonstration only runs on macOS
35+
- Windows 11, Windows 10, Windows 8.1, Windows 7 SP1
36+
37+
- Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012, and Windows Server 2008 R2
38+
39+
- macOS
40+
3641
- [Microsoft Defender Real-time protection is enabled](#verify-microsoft-defender-real-time-protection-is-enabled)
42+
3743
- [Behavior Monitoring is enabled](#enable-behavior-monitoring-for-microsoft-defender-for-endpoint)
3844

45+
## Windows
46+
47+
### Verify Microsoft Defender real-time protection is enabled
48+
49+
To verify real-time protection is enabled, open PowerShell as an administrator, and then run the following command:
50+
51+
```powershell
52+
get-mpComputerStatus |ft RealTimeProtectionEnabled
53+
```
54+
55+
When real-time protection is enabled, the result shows a value of `True`.
56+
57+
### Enable Behavior Monitoring for Microsoft Defender for Endpoint
58+
59+
For more information on how to enable Behavior Monitoring for Defender for Endpoint, see [how to enable Behavior Monitoring](/defender-endpoint/behavior-monitor).
60+
61+
### Demonstration of how Behavior Monitoring works in Windows and Windows Server
62+
63+
To demonstrate how Behavior Monitoring blocks a payload, run the following PowerShell command:
64+
65+
```powershell
66+
powershell.exe -NoExit -Command "powershell.exe hidden 12154dfe-61a5-4357-ba5a-efecc45c34c4"
67+
```
68+
69+
The output contains an expected error as follows:
70+
71+
```console
72+
hidden : The term 'hidden' is not recognized as the name of a cmdlet, function, script, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
73+
At line:1 char:1
74+
+hidden 12154dfe-61a5-4357-ba5a-efecc45c34c4
75+
+""""""
76+
CategoryInfo : ObjectNotFound: (hidden:String) [], CommandNotFoundException
77+
FullyQualifiedErrorId : CommandNotFoundException
78+
```
79+
80+
In the Microsoft Defender portal, in the Action center, you should see the following information:
81+
82+
- Windows Security
83+
- Threats found
84+
- Microsoft Defender Antivirus found threats. Get details.
85+
- Dismiss
86+
87+
If you select the link, your Windows Security app opens. Select **Protection history**.
88+
89+
You should see information that resembles the following output:
90+
91+
```console
92+
Threat blocked
93+
Detected: Behavior:Win32/BmTestOfflineUI
94+
Status: Removed
95+
A threat or app was removed from this device.
96+
Date: 6/7/2024 11:51 AM
97+
Details: This program is dangerous and executes command from an attacker.
98+
Affected items:
99+
behavior: process: C:\Windows\System32\WindowsPowershell\v1.0\powershell.exe, pid:6132:118419370780344
100+
process: pid:6132,ProcessStart:133621698624737241
101+
Learn more Actions
102+
```
103+
104+
In the [Microsoft Defender portal](https://security.microsoft.com), you should see information like this:
105+
106+
`Suspicious 'BmTestOfflineUI' behavior was blocked`
107+
108+
When you select it, you see the alert tree that has the following information:
109+
110+
`Defender detected and terminated active 'Behavior:Win32/BmTestOfflineUI' in process 'powershell.exe' during behavior monitoring`
111+
112+
## macOS
113+
39114
### Verify Microsoft Defender Real-time protection is enabled
40115

41116
To verify real-time protection (RTP) is enabled, open a terminal window and copy and execute the following command:
42117

43-
```bash
44-
mdatp health --field real_time_protection_enabled
45-
```
118+
```bash
119+
mdatp health --field real_time_protection_enabled
120+
```
46121

47122
When RTP is enabled, the result shows a value of 1.
48123

49124
### Enable Behavior Monitoring for Microsoft Defender for Endpoint
50125

51-
For more information on how to enable Behavior Monitoring for Defender for Endpoint, see [Deployment instructions](behavior-monitor-macos.md#deployment-instructions).
126+
For more information on how to enable behavior monitoring for Defender for Endpoint, see [Deployment instructions](behavior-monitor-macos.md#deployment-instructions).
52127

53128
### Demonstration of how Behavior Monitoring works
54129

@@ -63,7 +138,8 @@ To demonstrate how Behavior Monitoring blocks a payload:
63138
sleep 5
64139
```
65140

66-
2. Save as BM_test.sh
141+
2. Save as `BM_test.sh`.
142+
67143
3. Run the following command to make the bash script executable:
68144

69145
```bash
@@ -72,30 +148,32 @@ To demonstrate how Behavior Monitoring blocks a payload:
72148

73149
4. Run the bash script:
74150

75-
```bash
76-
sudo bash BM_test.sh
77-
```
151+
```bash
152+
sudo bash BM_test.sh
153+
```
78154

79-
The result shows:
155+
The result should look like this
80156

81-
zsh: killed sudo bash BM_test.sh
157+
`zsh: killed sudo bash BM_test.sh`
82158

83-
The file was quarantined by Defender for Endpoint on macOS. Use the following command to list all the detected threats:
159+
The file was quarantined by Defender for Endpoint on macOS. Use the following command to list all the detected threats:
84160

85-
```bash
86-
mdatp threat list
87-
```
161+
```bash
162+
mdatp threat list
163+
```
88164

89-
The result shows:
165+
The result shows information like this:
90166

91-
ID: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
167+
```console
168+
ID: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
92169

93-
Name: Behavior: MacOS/MacOSChangeFileTest
170+
Name: Behavior: MacOS/MacOSChangeFileTest
94171

95-
Type: "behavior"
172+
Type: "behavior"
96173

97-
Detection time: Tue May 7 20:23:41 2024
174+
Detection time: Tue May 7 20:23:41 2024
98175

99-
Status: "quarantined"
176+
Status: "quarantined"
177+
```
100178

101-
If you have Microsoft Defender for Endpoint P2/P1 or Microsoft Defender for Business, go to the [Microsoft Defender XDR portal](https://security.microsoft.com), and you'll see an alert named: "Suspicious 'MacOSChangeFileTest' behavior was blocked."
179+
If you have Microsoft Defender for Endpoint P2/P1 or Microsoft Defender for Business, go to the [Microsoft Defender portal](https://security.microsoft.com), and you see an alert titled, *Suspicious 'MacOSChangeFileTest' behavior was blocked*.

defender-office-365/air-custom-reporting.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,6 @@ appliesto:
3030

3131
With [Microsoft Defender for Office 365](mdo-about.md), you get [detailed information about automated investigations](air-view-investigation-results.md). However, some organizations also use a custom or third-party reporting solution. If your organization wants to integrate information about [automated investigations](air-about.md) with such a solution, you can use the Office 365 Management Activity API.
3232

33-
With [Microsoft Defender for Office 365](mdo-about.md), you get [detailed information about automated investigations](air-view-investigation-results.md). However, some organizations also use a custom or third-party reporting solution. If your organization wants to integrate information about automated investigations with such a solution, you can use the Office 365 Management Activity API.
34-
3533
|Resource|Description|
3634
|:---|:---|
3735
|[Office 365 Management APIs overview](/office/office-365-management-api/office-365-management-apis-overview)|The Office 365 Management Activity API provides information about various user, admin, system, and policy actions and events from Microsoft 365 and Microsoft Entra activity logs.|

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- m365-security
1616
- tier3
1717
ms.topic: reference
18-
ms.date: 12/29/2023
18+
ms.date: 06/09/2024
1919
---
2020

2121
# CloudAppEvents
@@ -65,6 +65,8 @@ For information on other tables in the advanced hunting schema, [see the advance
6565
| `AdditionalFields` | `dynamic` | Additional information about the entity or event |
6666
| `LastSeenForUser` | `string` | Shows how many days back the attribute was recently in use by the user in days (i.e. ISP, ActionType etc.) |
6767
| `UncommonForUser` | `string` | Lists the attributes in the event that are uncommon for the user, using this data to help rule out false positives and find out anomalies |
68+
| `AuditSource` | `string` | Audit data source, including one of the following: <br>- Defender for Cloud Apps access control <br>- Defender for Cloud Apps session control <br>- Defender for Cloud Apps app connector |
69+
| `SessionData` |`dynamic` | The Defender for Cloud Apps session ID for access or session control. For example: `{InLineSessionId:"232342"}` |
6870

6971
## Apps and services covered
7072

0 commit comments

Comments
 (0)