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
When enabling -x, --recover-records, duplicate entries are often outputted as for whatever reason the same event record is being read twice. Also, when doing investigations, analysts might want to load in old logs from backups, VSS, etc... so there is a chance of reading and outputting the same events. I want to be able to load in all of these backups evtx files and only output unique detections so in order to do this we need a -X, --remove-duplicate-detections option.
Under Output: in csv-timeline and json-timeline will be added -X, --remove-duplicate-detections Remove duplicate detections
In order to test, you can just make a copy of a evtx file and place the same two evtx files (with different names) in a folder and when -X is not used, it should output the same detections twice but when -X is used, it should not output the same detection more than once.
The text was updated successfully, but these errors were encountered:
When enabling
-x, --recover-records
, duplicate entries are often outputted as for whatever reason the same event record is being read twice. Also, when doing investigations, analysts might want to load in old logs from backups, VSS, etc... so there is a chance of reading and outputting the same events. I want to be able to load in all of these backups evtx files and only output unique detections so in order to do this we need a-X, --remove-duplicate-detections
option.Under
Output:
incsv-timeline
andjson-timeline
will be added-X, --remove-duplicate-detections Remove duplicate detections
In order to test, you can just make a copy of a evtx file and place the same two evtx files (with different names) in a folder and when
-X
is not used, it should output the same detections twice but when-X
is used, it should not output the same detection more than once.The text was updated successfully, but these errors were encountered: