How cayu/network-tools works
Project type and purpose
• This is a collection of networking‐maintenance and security‐auditing tools (a CLI “toolkit”) rather than a classic front-end/back-end application.
• It bundles three main components:
• auditoria: Python/Rust scripts for device inventory and compliance checks (e.g., Fortigate SOX audits, MAC‐to‐vendor lookup)
• minicom: serial‐port configuration profiles for connecting to various network devices (Cisco, Aruba, Fortinet, etc.)
• wazuh: custom decoders and rules to feed device logs into a Wazuh SIEM manager
Main components
a. User Workstation (where the CLI tools and configs live)
b. auditoria module
• FortigateSOX.py (Python script)
• inventario/mac_fabricante_pcap.rs (Rust‐based PCAP parser for inventory)
c. minicom profiles
• Serial console settings for each vendor
d. Network Devices
• Firewalls (Fortigate), switches (Cisco, Aruba, Extreme…), other vendors
e. Wazuh Manager
• custom_fortigate_decoders.xml
• custom_fortigate_rules.xml
f. Centralized SIEM / Log Storage (could be Elasticsearch, Splunk, etc.)
Relationships and data flows
• The User Workstation invokes auditoria scripts over SSH or API to network devices → gathers configurations, PCAPs, compliance status → optionally stores local reports.
• For out‐of‐band console access, the User Workstation uses minicom with the appropriate profile → serial connection to devices.
• Devices forward syslogs or audit logs to the Wazuh Manager → Wazuh applies the custom decoders/rules → alerts and parsed events are sent onward to the SIEM/Log Storage.
Architectural patterns & design principles
• Modular CLI toolkit: each folder is a standalone “plugin” or profile set.
• Separation of concerns:
• auditoria for active audits/inventory
• minicom for interactive console access
• wazuh for passive log‐analysis integration
• Configuration‐as‐code: profiles and rules are versioned alongside scripts.