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: docs/filters/filtering.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,8 @@ At its simplest form, a filter is composed of the LHS (Left Hand Side) and RHS (
9
9
kevt.category = 'net'
10
10
```
11
11
12
+
Boolean fields, that is the fields that always evaluate to either `true` or `false` can appear alone in the filter expression. For example, `pe.is_dll` is the short form of `pe.is_dll = true` expression.
13
+
12
14
The RHS expressions can be strings, numbers, IP addresses, boolean values, and fields. In the above snippet, the RHS is a simple string literal, but we could have written filters with the following RHS expressions:
Copy file name to clipboardExpand all lines: docs/filters/prefiltering.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,10 @@ The above is the summary of configuration options that influence the collection
11
11
-`enable-image` enables/disables the collection of image loading/unloading events
12
12
-`enable-handle` enables/disables the collection of handle events
13
13
-`enable-audit-api` enables/disables kernel audit API calls events
14
-
-`enable-antimalware-engine` enables/disables Antimalware Engine events, which primarily provide a source of [driver-loading](kevents/driver.md) events
14
+
-`enable-mem` enables/disables the collection of memory events
15
+
-`enable-dns` enables/disables DNS telemetry
15
16
16
-
### Blacklisting {docsify-ignore}
17
+
### Excluding processes or events {docsify-ignore}
17
18
18
19
If you want to permanently exclude specific events or processes that produce them from the event flow, you can achieve this by defining the blacklist in the `kstream.blacklist` configuration section:
Copy file name to clipboardExpand all lines: docs/kevents/driver.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,7 @@
2
2
3
3
#### LoadDriver
4
4
5
-
Driver loading events are triggered when the driver object is loaded into the kernel. The `image_name` parameter represents the full path of the driver file located in the file system.
6
-
Driver events are consumed from the `Microsoft Antimalware Engine` ETW provider, thus the events are only published if the Windows Defender Antivirus realtime protection is activated.
5
+
Driver loading events are triggered when the driver object is loaded into the kernel. Regular `LoadImage` events are triggered when the kernel driver is loaded or when the driver is unloaded, the `UnloadImage` event is received.
7
6
8
7
An alternative route for detecting driver loading events is based on observing the [handle manager](kevents/handle.md) events. For example, a filter expression for pinpointing such events could be arranged as follows.
0 commit comments