Major Perf PoolScan physical layer#1949
Open
forensicxlab wants to merge 4 commits intovolatilityfoundation:developfrom
Open
Major Perf PoolScan physical layer#1949forensicxlab wants to merge 4 commits intovolatilityfoundation:developfrom
forensicxlab wants to merge 4 commits intovolatilityfoundation:developfrom
Conversation
…plugins to scan pool tags on the physical memory layer () instead of broad Win10/11 virtual scan range.
Contributor
Author
|
Hi, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR addresses major performance issues I am facing in Windows 10/11 memory images for poolscan-based plugins (for example windows.filescan).
Poolscan consumers currently scan the Win10/11 virtual kernel layer by default, which can traverse very large sparse address ranges and spend most time in translation/read overhead before yielding results.
We have added an optional scan_layer_name parameter to the following:
PoolScanner.generate_pool_scan_extendedPoolScanner.generate_pool_scanWe updated poolscan-based Windows plugins to pass
memory_layerwhen available (fallback to original layer if not):windows.filescan.FileScanwindows.psscan.PsScanwindows.thrdscan.ThrdScanwindows.driverscan.DriverScanwindows.modscan.ModScanwindows.mutantscan.MutantScanwindows.symlinkscan.SymlinkScanwindows.netscan.NetScanwindows.callbacks.Callbackswindows.windowstations.WindowStationswindows.registry.hivescan.HiveScan(poolscan path).windows.filescan
previous behavior: timed out at 3600s in control run
patched: finished in ~68.8s, 5666 results
windows.psscanprevious behavior: timed out at 3600s, 0 results
patched: finished in ~63.6s, 286 results
I can privately share a sample image to do test. Let me know by contacting me at felix.guyard@forensicxlab.com.
Kind regards.