initial README
This commit is contained in:
17
README.md
17
README.md
@@ -1,5 +1,8 @@
|
|||||||
# FACTUM-NOTES
|
# FACTUM-NOTES
|
||||||
**Cryptographically Secured Forensic Logging Utility**
|
|
||||||
|
Cryptographically Secured Forensic Logging Utility
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -16,16 +19,20 @@ Designed for operation in forensic-grade, air-gapped environments, the system en
|
|||||||
The design of Factum-Notes prioritizes integrity, low-latency input, and deployment flexibility.
|
The design of Factum-Notes prioritizes integrity, low-latency input, and deployment flexibility.
|
||||||
|
|
||||||
### Core Integrity Mechanisms
|
### Core Integrity Mechanisms
|
||||||
|
|
||||||
* **Immutable Logging:** All entries are subjected to immediate SHA-256 hashing.
|
* **Immutable Logging:** All entries are subjected to immediate SHA-256 hashing.
|
||||||
* **Cryptographic Non-Repudiation:** Entries are signed using the analyst's local GPG private key.
|
* **Cryptographic Non-Repudiation:** Entries are signed using the analyst's local GPG private key.
|
||||||
* **Temporal Verification:** Precise timestamping accompanies all signatures to establish a chronological sequence of events.
|
* **Temporal Verification:** Precise timestamping accompanies all signatures to establish a chronological sequence of events.
|
||||||
|
|
||||||
### User Interface Paradigm
|
### User Interface Paradigm
|
||||||
|
|
||||||
The system implements a hybrid interface model:
|
The system implements a hybrid interface model:
|
||||||
|
|
||||||
* **CLI (Command Line Interface):** Optimized for high-velocity data entry and rapid logging during active forensic acquisition.
|
* **CLI (Command Line Interface):** Optimized for high-velocity data entry and rapid logging during active forensic acquisition.
|
||||||
* **GUI (Graphical User Interface):** A lightweight PySide6 interface for complex case management, artifact linking, and review.
|
* **GUI (Graphical User Interface):** A lightweight PySide6 interface for complex case management, artifact linking, and review.
|
||||||
|
|
||||||
### Deployment Specifications
|
### Deployment Specifications
|
||||||
|
|
||||||
* **Single-Binary Distribution:** Compiled to a standalone executable to eliminate dependency conflicts.
|
* **Single-Binary Distribution:** Compiled to a standalone executable to eliminate dependency conflicts.
|
||||||
* **Air-Gap Optimization:** Designed to function with zero network dependencies post-installation.
|
* **Air-Gap Optimization:** Designed to function with zero network dependencies post-installation.
|
||||||
* **Cross-Platform Compliance:** Fully validated for operation on Linux and Windows NT-family kernels.
|
* **Cross-Platform Compliance:** Fully validated for operation on Linux and Windows NT-family kernels.
|
||||||
@@ -35,19 +42,23 @@ The system implements a hybrid interface model:
|
|||||||
## FUNCTIONAL SPECIFICATIONS
|
## FUNCTIONAL SPECIFICATIONS
|
||||||
|
|
||||||
### Case & Evidence Management
|
### Case & Evidence Management
|
||||||
|
|
||||||
* **Hierarchical Structure:** Supports multiple unique cases, each containing distinct evidence containers.
|
* **Hierarchical Structure:** Supports multiple unique cases, each containing distinct evidence containers.
|
||||||
* **Metadata Association:** optional storage of cryptographic hashes (MD5, SHA1, SHA256) for all associated evidence objects.
|
* **Metadata Association:** optional storage of cryptographic hashes (MD5, SHA1, SHA256) for all associated evidence objects.
|
||||||
* **Tagging Taxonomy:** Implements a user-defined tagging system for cross-referencing findings across the dataset.
|
* **Tagging Taxonomy:** Implements a user-defined tagging system for cross-referencing findings across the dataset.
|
||||||
|
|
||||||
### Automated Parsing
|
### Automated Parsing
|
||||||
|
|
||||||
* **IoC Extraction:** Integrated regex-based parsing to identify and catalog Indicators of Compromise (IP addresses, hashes, domains, crypto-currency entities) from textual notes.
|
* **IoC Extraction:** Integrated regex-based parsing to identify and catalog Indicators of Compromise (IP addresses, hashes, domains, crypto-currency entities) from textual notes.
|
||||||
* **Filtering Logic:** Boolean search capabilities across tags and extracted IoCs.
|
* **Filtering Logic:** Boolean search capabilities across tags and extracted IoCs.
|
||||||
|
|
||||||
### Export Capabilities
|
### Export Capabilities
|
||||||
|
|
||||||
* **Scoped Reporting:** Generation of reports limited to specific cases or evidence sets.
|
* **Scoped Reporting:** Generation of reports limited to specific cases or evidence sets.
|
||||||
* **Format Support:** Output availability in raw text and Markdown formats for integration into final forensic reports.
|
* **Format Support:** Output availability in raw text and Markdown formats for integration into final forensic reports.
|
||||||
|
|
||||||
### Key Management
|
### Key Management
|
||||||
|
|
||||||
* **System Integration:** Direct interfacing with the host operating systems GPG keychain (Gpg4win/GnuPG/Kleopatra).
|
* **System Integration:** Direct interfacing with the host operating systems GPG keychain (Gpg4win/GnuPG/Kleopatra).
|
||||||
|
|
||||||
---
|
---
|
||||||
@@ -68,11 +79,13 @@ The application is constructed upon a modern, verified stack to ensure maintaina
|
|||||||
The following modules are proposed for medium-term integration:
|
The following modules are proposed for medium-term integration:
|
||||||
|
|
||||||
### Heuristic Analysis Engine (LLM Integration)
|
### Heuristic Analysis Engine (LLM Integration)
|
||||||
|
|
||||||
* **Goal Definition:** Analyst-defined investigative objectives per case.
|
* **Goal Definition:** Analyst-defined investigative objectives per case.
|
||||||
* **Automated Summarization:** Synthesis of complex note chains into executive summaries.
|
* **Automated Summarization:** Synthesis of complex note chains into executive summaries.
|
||||||
* **Procedural Guidance:** Algorithmic suggestions for next steps based on current findings and defined goals.
|
* **Procedural Guidance:** Algorithmic suggestions for next steps based on current findings and defined goals.
|
||||||
|
|
||||||
### Extended Functionality
|
### Extended Functionality
|
||||||
|
|
||||||
* **Search Indexing:** Full-text search across the encrypted database.
|
* **Search Indexing:** Full-text search across the encrypted database.
|
||||||
* **IoC Enrichment:** External API lookup for extracted indicators (optional network connectivity required).
|
* **IoC Enrichment:** External API lookup for extracted indicators (optional network connectivity required).
|
||||||
* **Remote Collaboration:** Synchronization capabilities via remote database backends for multi-analyst teams.
|
* **Remote Collaboration:** Synchronization capabilities via remote database backends for multi-analyst teams.
|
||||||
@@ -82,7 +95,7 @@ The following modules are proposed for medium-term integration:
|
|||||||
|
|
||||||
## COPYRIGHT & LICENSE
|
## COPYRIGHT & LICENSE
|
||||||
|
|
||||||
**Copyright © 2025**
|
Copyright © 2025
|
||||||
|
|
||||||
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
|
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
|
||||||
|
|
||||||
|
|||||||
0
project.toml
Normal file
0
project.toml
Normal file
BIN
resources/gemini-logo.png
Normal file
BIN
resources/gemini-logo.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.1 MiB |
Reference in New Issue
Block a user