I have added to evtxtoelk.py script the option to write the output to a .json file, this allows to ingest such events by any logcollector software that supports JSON, e.g. Wazuh.
I have tested all included or modified methods with ELK 7.9.1 (All seems to work as expected).
Some examples:
Event from security event channel in JSON format (from output file)
I tried to modify the options less than possible so I changed ELK IP parameter to output that let the user introduce the combination of IP:PORT option or JSON filename (finished in .json) to select output method.
Execution example:
To JSON file:
python .\evtxtoelk.py .\security.evtx security.json
6184 events exported to security.json
To ELK:
python .\evtxtoelk.py .\security.evtx 192.168.2.10
Bulking final set of records to ES: 1
.
.
.
Kibana discover example
I have also added a debug option to see the processed events in the JSON output.
I hope it will help to solve some data ingestion related issues.
Hello!,
I have added to evtxtoelk.py script the option to write the output to a
.json
file, this allows to ingest such events by any logcollector software that supports JSON, e.g. Wazuh.I have tested all included or modified methods with ELK 7.9.1 (All seems to work as expected). Some examples: Event from security event channel in JSON format (from output file)
I tried to modify the options less than possible so I changed ELK IP parameter to
output
that let the user introduce the combination ofIP:PORT
option or JSON filename (finished in.json
) to select output method. Execution example: To JSON file:To ELK:
Kibana discover example
I have also added a debug option to see the processed events in the JSON output. I hope it will help to solve some data ingestion related issues.
Regards!.