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
We compute all features separately and only rely on the `domain` and `class` for binary classification.
204
-
205
188
### Inserting Data for Testing
206
189
207
-
For testing purposes, you can ingest PCAPs or tap on network interfaces using the zeek-based sensor in its `1.0.0` release. For more information on it, please refer to [the documentation](https://github.com/Hamstring-NDR/hamstring-zeek).
190
+
For testing purposes, you can ingest PCAPs or tap on network interfaces using the zeek-based sensor that is integrated into the docker-compose file. For more information on the sensor, please refer to [the documentation](https://github.com/Hamstring-NDR/hamstring-zeek).
208
191
209
192
### Training Your Own Models
210
193
@@ -260,33 +243,6 @@ The results will be saved per default to `./results`, if not configured otherwis
260
243
```
261
244
This will create a `rules.txt` file containing the innards of the model, explaining the rules it created.
262
245
263
-
<p align="right">(<a href="#readme-top">back to top</a>)</p>
264
-
265
-
266
-
### Data
267
-
268
-
> [!IMPORTANT]
269
-
> We support custom schemes.
270
-
271
-
Depending on your data and usecase, you can customize the data scheme to fit your needs.
272
-
The below configuration is part of the [main configuration file](./config.yaml) which is detailed in our [documentation](https://HAMSTRING.readthedocs.io/en/latest/usage.html#id2)
0 commit comments