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: microsoft_sysmon/README.md
+25-22Lines changed: 25 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Run powershell.exe as admin and execute the following command:
40
40
sourcecategory: windowsevent
41
41
```
42
42
43
-
See the [sample microsoft_sysmon.d/conf.yaml][9] for available configuration options.
43
+
See the [sample microsoft_sysmon.d/conf.yaml][11] for available configuration options.
44
44
45
45
3. [Restart the Agent][3].
46
46
@@ -50,31 +50,32 @@ Follow these steps to install Sysmon:
50
50
1. Download the zip file from the [Sysmon download page][4]. Extract its zip file content.
51
51
2. Create an XML file for configuring Sysmon. For example, if you want to monitor processes created by apps from AppData folders, the configuration file will look like content shown below. You can add more event filters under the `EventFiltering` XML tag for other events in the same way.
3. Execute the command as admin from the extracted folder:
66
+
**Note:** Sysmon is highly configurable using the XML configuration file, which allows you to:
67
+
- Control which events to monitor
68
+
- Filter events based on processes, paths, etc.
65
69
66
-
```powershell
67
-
.\Sysmon -i [<configfile>]
68
-
```
70
+
Enabling too many Sysmon event types can lead to excessive data ingestion. Community resources such as [sysmon-modular][9] and the [SwiftOnSecurity Sysmon config][10] provide recommended configurations, including examples of event inclusions and exclusions. These are intended as a starting point, and you can refer to them when tuning your own configuration.
69
71
70
-
**Note:** Sysmon is highly configurable using the configuration (XML) file which allows you to:
71
-
- Control which events to monitor
72
-
- Filter events based on processes, paths, etc.
72
+
3. Run the following command as admin from the extracted folder:
73
73
74
-
Enabling too many event types can result in excessive data ingestion. Only critical security events should be enabled based on the threat model and monitoring needs.
75
-
These events should be selectively enabled for critical system directories, processes, and users to avoid unnecessary log noise.
74
+
```powershell
75
+
.\Sysmon -i [<configfile>]
76
+
```
76
77
77
-
For more details on configuration, please refer to the [Sysmon docs][7].
78
+
For more details, please refer to the [Sysmon docs][7].
78
79
79
80
### Validation
80
81
@@ -117,4 +118,6 @@ Need help? Contact [Datadog support][1].
0 commit comments