Integrate master IOC unifier engine and refactor container paths#2
Open
sergiofoz wants to merge 2 commits into
Open
Integrate master IOC unifier engine and refactor container paths#2sergiofoz wants to merge 2 commits into
sergiofoz wants to merge 2 commits into
Conversation
…/memory phases data lifecycle
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
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.
Overview
This Pull Request introduces the Master IOC Unifier Engine and ensures a production-ready, clean data lifecycle across all analysis phases. It also resolves path inconsistencies in the main orchestrator by aligning them with the infrastructure Wiki guidelines.
Key Changes
IOCReportUnifiermodule (utils/report_unifier.py). It automatically aggregates telemetry from Phase 1 (Static Analysis), Phase 2 (Dynamic Analysis via CAPEv2), and Phase 3 (Memory Forensics via Volatility 3) into a single structured master report namedunified_maestro_report.json.ioc_extractor.py, switching paths and internal naming conventions to English as specified in the team's deployment architecture documentation..gitignoreto strictly exclude malware samples (bin_samples/), local execution outputs (bin_outputs/), and Python cache files (__pycache__), ensuring no data leaks hit the public repository.Verification & Testing (Smoke Tests)
Comprehensive end-to-end testing was performed locally on the CAPE VM (
vm-cape) with 100% success:./ioc_extractor.py --help.eicar.com. The engine successfully parsed the static data and handled edge cases properly (e.g., gracefully logging empty process listings or missing PIDs in ephemeral payloads without crashing).second_stage.exe. The script completed all orchestration phases safely, accurately mapped the dynamic registry and file system hooks, and successfully generated a pristineunified_maestro_report.jsoncompiling the multi-phase IoCs.Related Artifacts Created
utils/__init__.pyutils/report_unifier.pyioc_extractor.py.gitignore