How 0xcgz/project-mursad works
Project type & purpose (what you’re diagramming)
Project Mursad is not a typical “codebase application” architecture; it’s an enterprise security lab / SOC telemetry environment implemented as virtualized infrastructure on Proxmox, with:
• Network perimeter & segmentation via pfSense (VLANs/bridges, DMZ vs LAN isolation)
• Enterprise identity via Active Directory Domain Services (DC/DNS)
• Telemetry + detection via Wazuh SIEM (manager/indexer/dashboard + agents + syslog ingestion)
• Adversary simulation / validation via Kali Linux
• Later-stage endpoint protection / EDR (Kaspersky Security Center, antivirus integration)
• IDS/IPS as a dedicated control plane (often Suricata/Snort on pfSense or a separate sensor VM)
Where components live (Proxmox nodes, VMs, VLANs, NICs/bridges)
2) How signals flow (logs/telemetry to SIEM, management traffic, user traffic crossing zones)
The file tree is documentation-oriented (no app source code):
• docs/ → where phase-by-phase build docs/architecture notes should live (even if empty now)
• configs/ → intended to store pfSense exports, Wazuh configs, AD/GPO notes, IDS rules, syslog configs
• scripts/ → automation (Proxmox provisioning, agent rollout, hardening scripts, benchmark scripts)
Main components to include (break the system into as many components as possible)
Based on README phases, your canonical component list should include at least:
Infrastructure
• Bare-metal server
• Proxmox hypervisor
• Virtual networking (bridges, VLAN trunk)
• VM templates / images (if used)
Perimeter & segmentation
• pfSense firewall/router
• WAN interface
• LAN interface
• DMZ interface
• VLAN interfaces
• NAT, firewall rules, static routes
Identity / core services
• Windows Server Domain Controller
• AD DS
• DNS (and possibly DHCP)
• Internal DNS resolution path(s) (LAN vs DMZ)
SOC / telemetry
• Wazuh components (explicitly split them):
• Wazuh Manager
• Indexer (OpenSearch/Elastic)
• Dashboard
• Syslog forwarders / collectors (if separate)
• Time sync (NTP) source (important for SOC accuracy)
Detection / prevention
• IDS/IPS engine (Suricata/Snort)
• Sensor placement (on pfSense vs dedicated VM “tap” / SPAN-like approach)
Endpoints & validation
• Windows clients/servers in LAN
• DMZ servers (intentionally vulnerable services)
• Kaspersky Security Center + endpoint agents (Phase 4)
External dependencies
• ISP/Internet
• External DNS (if used)
• Threat intel feeds (if Wazuh/IDS pulls any)
• Update repos (Windows Update, Linux repos)
Architectural patterns to explicitly show
This lab implies several key patterns—make them visually obvious:
• Defense-in-depth: perimeter firewall + segmentation + IDS + SIEM + EDR
• Network zoning / trust boundaries: WAN vs LAN vs DMZ (and optionally MGMT/SOC)
• Centralized telemetry: many-to-one log aggregation into Wazuh
• Control plane vs data plane separation: management access should not traverse DMZ casually
• Phased build-out: matches the README phases; components appear over time
Phase roadmap view
Store exported images in assets/, and cross-link them from docs/ as the build progresses.