# anldori/system-security-lab architecture

> Architecture diagram of the GitHub repository anldori/system-security-lab, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-02). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/anldori/system-security-lab
- Repository: https://github.com/anldori/system-security-lab

## Overview

##### Project Type and Purpose
- The lab manual is designed to simulate or guide the setup of a security environment.
- It involves multiple systems (e.g., Hacking Machine, ITOP, Jump-Server, Splunk, VPN, Wazuh, and Zero Tier as VPN) that each play a role in security operations—ranging from attack simulation (Hacking Machine) to monitoring and log analysis (Splunk, Wazuh), secure remote access (VPN, Zero Tier), and network/system management (ITOP, Jump-Server).

##### Analyzing the File Structure
- Each top-level directory corresponds to a different security component or tool.
- The “Hacking Machine” might represent an attack platform used for penetration testing.
- “ITOP” could be associated with automation of system operations (evidenced by its automation shell script).
- “Jump-Server” is included as a means to access internal networks securely.
- “Splunk” and “Wazuh” serve monitoring/analytic roles, with Splunk focusing on log aggregation and Wazuh on security monitoring.
- “VPN” and “Zero Tier as VPN” indicate two methods for establishing secure remote connections.
- Presence of README files in each directory suggests that each component is modular and documented separately, hinting at a modular design.

a. Main Components:
- Hacking Machine (attacker/simulation system)
- ITOP (automation and operational management)
- Jump-Server (bastion host for secure access)
- Splunk (logging/aggregated SIEM system)
- Wazuh (security monitoring and intrusion detection)
- VPN and Zero Tier as VPN (secure network tunnels)

b. Relationships and Interactions:
- Hacking Machine interacting with target systems or being used to simulate penetration attempts.
- Jump-Server to the secure networking layer provided by both the VPN and Zero Tier solutions.
- That ITOP may manage or automate configurations across various systems.
- Data flows from network events or logs to Splunk and Wazuh, which would centralize logging and monitor threats.

c. Key Architectural Patterns/Design Principles:
- Modularity by representing each component as a standalone module.
- Separation of concerns: one module handles attack simulation (Hacking Machine), others handle secure access (VPN, Zero Tier, Jump-Server), and yet others focus on monitoring and automation (Splunk, Wazuh, ITOP).
- If applicable, note any automation or orchestration that might occur via ITOP’s script(s).

d. Relevant Technologies or Frameworks:
- While the exact internal technologies are not detailed in the file tree, labels should indicate that typical security and monitoring frameworks are used (for instance, Splunk and Wazuh are industry-standard tools).

##### Elements
- Data flow from the Hacking Machine into security monitoring systems.
- Control and management flows from ITOP.
- Secure access paths linking the jump-server with the VPN solutions.
- Logging and alert flows between monitored endpoints and Splunk/Wazuh.
- Grouping related components (for instance, grouping VPN and Zero Tier as VPN under a “Secure Connectivity” section).

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Attack Simulation"
        HM["Hacking Machine"]:::hacking
    end

    subgraph "Automation & Management"
        ITOP["ITOP Automation"]:::automation
    end

    subgraph "Access Layer"
        JS["Jump-Server (Bastion)"]:::bastion
    end

    subgraph "Monitoring Systems"
        SP["Splunk (SIEM)"]:::monitoring
        WA["Wazuh (Security Monitoring)"]:::monitoring
    end

    subgraph "Secure Connectivity"
        VPN["VPN (Secure Remote Access)"]:::vpn
        ZT["Zero Tier VPN (Alternative Secure Connectivity)"]:::vpn
    end

    %% Connections
    HM -->|"sends_alerts"| WA
    HM -->|"sends_logs"| SP
    ITOP -->|"configures"| JS
    JS -->|"secure_access"| VPN
    JS -->|"secure_access"| ZT

    %% Click Events
    click HM "https://github.com/anldori/system-security-lab/blob/main/Hacking Machine/README.MD"
    click ITOP "https://github.com/anldori/system-security-lab/blob/main/ITOP/itop_automation_ubuntu.sh"
    click JS "https://github.com/anldori/system-security-lab/blob/main/Jump-Server/README.MD"
    click SP "https://github.com/anldori/system-security-lab/blob/main/Splunk/README.MD"
    click WA "https://github.com/anldori/system-security-lab/blob/main/Wazuh/README.MD"
    click VPN "https://github.com/anldori/system-security-lab/blob/main/VPN/README.MD"
    click ZT "https://github.com/anldori/system-security-lab/blob/main/Zero Tier as VPN/README.MD"

    %% Styles
    classDef hacking fill:#ffcccc,stroke:#cc0000,stroke-width:2px;
    classDef automation fill:#cce5ff,stroke:#004085,stroke-width:2px;
    classDef bastion fill:#fff3cd,stroke:#856404,stroke-width:2px;
    classDef monitoring fill:#d4edda,stroke:#155724,stroke-width:2px;
    classDef vpn fill:#d1ecf1,stroke:#0c5460,stroke-width:2px;
```
