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
Originally posted by sak-improsec May 2, 2023
Hi Eric,
My team and I have been using KAPE for almost a year, and have built our forensic platform around it.
One thing I would like to request is the ability for the --asu flag to drop the target and module output in the same folder in Azure, rather than one for target and one for module:
Usecase: Full triage image uploaded to azure, along with live queries from modules like netstat, pslist, ip-config, and so on, and not having to build logic around which live data is correlated with a specific triage image.
My current "solution" is to "sneak" the module output in with the target by setting --mdest to --tdest/moduleoutput/ and as KAPE zips everything in --tdest, everything will be included. But im not a fan of this hacked way of doing it.
The text was updated successfully, but these errors were encountered:
Discussed in #793
Originally posted by sak-improsec May 2, 2023
Hi Eric,
My team and I have been using KAPE for almost a year, and have built our forensic platform around it.
One thing I would like to request is the ability for the --asu flag to drop the target and module output in the same folder in Azure, rather than one for target and one for module:
Usecase: Full triage image uploaded to azure, along with live queries from modules like netstat, pslist, ip-config, and so on, and not having to build logic around which live data is correlated with a specific triage image.
My current "solution" is to "sneak" the module output in with the target by setting --mdest to --tdest/moduleoutput/ and as KAPE zips everything in --tdest, everything will be included. But im not a fan of this hacked way of doing it.
The text was updated successfully, but these errors were encountered: