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
Check out the `examples` folder for more examples.
56
+
## Matching nested fields
57
+
58
+
You can access nested fields by using a dot `.` as a separator. For example, if you have an event like
59
+
60
+
```json
61
+
{
62
+
"Event": {
63
+
"ID": 42
64
+
}
65
+
}
66
+
```
67
+
68
+
you can access the `ID` field by using `Event.ID` in the Sigma rule. Note, that fields containing a dot take
69
+
precedence over nested fields. For example, if you have an event like
70
+
71
+
```json
72
+
{
73
+
"Event.ID": 42,
74
+
"Event": {
75
+
"ID": 43
76
+
}
77
+
}
78
+
```
79
+
80
+
the engine will evaluate `Event.ID` to 42.
54
81
55
82
## Strong type checking
56
83
@@ -73,7 +100,6 @@ selection_2:
73
100
condition: 1 of them
74
101
```
75
102
76
-
77
103
## License
78
104
79
105
Licensed under either of
@@ -87,4 +113,5 @@ at your option.
87
113
88
114
Contributions are welcome! Please open an issue or create a pull request.
89
115
90
-
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
116
+
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as
117
+
defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
0 commit comments