How sameerfakhoury/forenzmap works
Project Type and Purpose
• ForenZmap is a command-line tool focused on extracting, parsing, and visualizing key Windows registry data (from SYSTEM.hiv and SOFTWARE.hiv files) for forensic analysis.
• Its primary functionality is to parse 14 significant registry keys, decode time-related values, and present the results as a mind map in an HTML report.
Key Components
a. Main Application Entry Point:
• Main script (ForenZmap.py) that initializes the tool and handles user inputs.
b. Core Modules (located in _ForenZmap_Code):
• Module for Application logic: _ForenZmap_Application.py
• Banner and UI handling: _ForenZmap_Banner.py and _ForenZmap_Interface.py
• Specific registries or keys parsers such as ComputerName, ConnectionsHistory, Policies, ProfileList, ShellFolders, Winlogon, and others.
• Mind Map Generation: _ForenZmap_MindMap.py (which later feeds into the HTML report creation).
• Modules handling data extraction, analyses, and possibly decoding (e.g., TimeZoneInformation, CurrentVersion).
c. Dependency Management and External Libraries:
• The requirements.txt indicates that any external dependencies (like libraries for parsing or HTML generation) should also be acknowledged.
d. Input/Output and User Interaction:
• Input: User-supplied paths to the hives.
• Output: HTML report with a mind map visualization.
e. Supporting Components:
• Modules such as _ForenZmap_Run.py, _ForenZmap_Select.py which may control the flow of execution.
• Additional modules (e.g., _ForenZmap_Exclusions.py, _ForenZmap_NetworkCards.py) that are likely dedicated to specific data extraction routines.
Technological and Architectural Choices
• The project follows a modular design where each Python file encapsulates a portion of the forensic data extraction or visualization process.
• Although it’s a CLI tool, there is an implicit separation of the user interface (output banners and input prompts) from the core parsing and processing logic.
• The design also reflects a layered approach:
• User Interface Layer: Handles inputs, outputs, and initial instructions.
• Application/Control Layer: Coordinates the operation between reading input files, invoking various parsing modules, and managing the overall workflow.
• Data/Processing Layer: Contains the actual business logic for parsing registry data, performing extractions, and generating the visualization (both the mind map and the HTML report).