Added artifacts to make it easier to post process KapeFiles.Targets #3693
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Windows.KapeFiles.Targets artifact allows to collect many bulk forensic artifacts like registry hives etc. People often use it to collect offline collections for preservation of hosts.
Although best practice is to also collect parsing artifacts as the same time, sometimes this is left out. In this case the user needs to parse the collected raw files (for example collecting $MFT then needing to apply
Windows.NTFS.MFT
to parse it). This is not always easy to do.This PR adds a notebook suggestion which applies remapping on the KapeFiles collection in such as way that some regular artifacts designed to run on the live system can work to some extent off the raw collection. The additional parsing will be added to new collections in the same (possibly virtual) client.
Also: Bugfix for zip_nocase accessor failed to work in some cases.
Since we now use remapping there is no need for the Linux.KapeFiles.CollectFromDirectory (which was basically the same as the Windows.KapeFiles.Targets but applies to a mounted directory). That artifact is now removed.