Why build a framework? Oftentimes, we perform the same series of steps for a given piece of evidence. For example, we commonly prepare reports for link, prefetch, and jumplist files, examine registry keys, and establish external devices and network activity to answer forensic questions. As we've seen, we can develop a script to parse these artifacts for us and display the data in a format conducive for rapid analysis. Why not write a series of scripts, each responsible for one artifact, and then control them with a singular script, to execute all at once, and thus further automate our analysis?
A framework can be developed to run a series of scripts and parse multiple artifacts with a single command. The output of such a framework could be a series of analysis-ready spreadsheets. This allows the examiner to skip the same tedious series of steps to process items and start answering meaningful questions about the evidence
Frameworks typically have three main components:
A main controller...