How ahsan9267/cyber-investigation-state-model-for-ai-assisted-cyber-incident-investigation works
This snapshot implements the telemetry foundation of an AI-assisted SOC investigation system, not the later investigation workflow. The documented runtime path collects Windows events through Wazuh and network traffic through Suricata, then forwards telemetry to the Wazuh Manager. The README also names Wi-Fi and VirtualBox lab monitoring and a diagnostic Suricata rule. Configuration files are present, but their exact runtime wiring is not shown. Ingestion, case association, investigation state, evidence analysis, AI assistance, and analyst validation are described as later stages, not implemented components here.
Main entry points: fyp-test.rules Diagnostic rule
Components 11
Endpoint telemetry
- Sysmon
- Windows Event Channel
Network telemetry
- Npcap capture
- Suricata IDS
- Wi-Fi monitoring
- VirtualBox lab monitoring
- EVE JSON
Event collection
- Wazuh Agent
- Wazuh Manager
Configuration
- Diagnostic rule
config/suricata/fyp-test.rules - Collection XML example
config/wazuh/ossec-collection-example.xml
Connections 7
- Sysmon → Windows Event Channel: emits events
README.md - Windows Event Channel → Wazuh Agent: collects events
README.md - Wazuh Agent → Wazuh Manager: forwards TCP 1514
README.md - Npcap capture → Suricata IDS: provides capture
README.md - Suricata IDS → EVE JSON: generates JSON
README.md - EVE JSON → Wazuh Agent: forwards events
README.md - Diagnostic rule → Suricata IDS: supports diagnostic detection
README.md