CyberAI
An ongoing local-inference cybersecurity environment focused on private, on-device intelligence. Integrates Ollama, Qwen3-Coder 30B, and OpenCode with Kali Linux security tooling to orchestrate multi-agent development workflows, automated vulnerability analysis tasks, and reproducible security experimentation.
Standardized Case Study Specification (13 Parameters)
What is CyberAI?
psychology Purpose & Problem Solved
Security operations generate vast quantities of operational telemetry: system authentication attempts (`auth.log`), kernel messages, firewall connection drops, and security utility outputs. Analyzing these raw, unstructured logs manually during incident investigations or lab exercises is time-consuming and error-prone.
The portfolio project documentation describes CyberAI as a private, on-device telemetry ingestion and triage platform. It ingests raw logs, normalizes them into structured incident timelines, and applies contextual anomaly detection heuristics combined with local neural reasoning to identify correlated attack patterns.
shield Privacy & Air-Gapped Philosophy
Security telemetry frequently contains sensitive IP addresses, usernames, hostnames, and password hash attempts. Sending these logs to cloud-based LLM APIs presents significant data exposure risks.
CyberAI guarantees complete data residency by executing Qwen3-Coder 30B locally via Ollama on Kali Linux. Telemetry is parsed, correlated, and triaged entirely in an air-gapped local environment with zero external telemetry.
Bridges Kali Linux security tools with private local LLM reasoning via OpenCode and Ollama, transforming raw forensic streams into structured operational insight.
Documented System Architecture
Based on the documented architecture in the portfolio engineering specifications, CyberAI structures telemetry ingestion and local reasoning through an end-to-end pipeline:
- • Linux `auth.log` & Syslog
- • Firewall Packet Dumps
- • Security Tool Logs
- • Regex & Token Parser
- • Chronological Sequencing
- • Heuristic Anomaly Flags
- • Ollama Inference Server
- • Threat Correlation
- • Contextual Risk Scoring
- • Multi-Agent Workflows
- • Incident Reports
- • Prioritized Alerts
Component Breakdown & Data Flow
| Component | Responsibility | Inputs | Outputs | Relationships |
|---|---|---|---|---|
| Log Parser & Normalizer | Extracts timestamps, hostnames, IPs, and event types from raw log files. | Raw log files (syslog, auth.log) | Structured JSON event stream | Feeds into Chronological Timeline Engine |
| Timeline & Anomaly Engine | Organizes events sequentially and applies heuristic threshold triggers. | Structured event stream | Chronological timeline with anomaly flags | Passes prioritized context to local AI model |
| Threat Correlation (Qwen3-Coder 30B) | Analyzes multi-stage event sequences to evaluate potential attack progression. | Incident timeline windows | Threat correlation summaries & risk scores | Hosted via local Ollama runtime |
| OpenCode Agent Integrator | Orchestrates multi-agent development workflows and automated analysis tasks. | Correlation output, user instructions | Automated tasks, investigative queries | Integrates with Kali Linux security utilities |
Documented Operational Workflow
Raw system logs (such as authentication events, firewall connection logs, or tool dumps) are ingested into the platform.
Events are structured into normalized schemas and chronologically ordered to form a coherent activity timeline.
Qwen3-Coder 30B evaluates clustered events, correlating anomalous patterns (e.g. repeated auth failures followed by escalation).
OpenCode agents dispatch follow-up verification tasks or query specific log subsets for deep contextual inspection.
Generates structured security incident reports with risk scores and actionable defensive remediation recommendations.
Technologies & Architecture Implementation
Engineered in Python with custom parsers for common Linux log formats (syslog, auth.log, auditd, iptables). Normalizes timestamps into unified UTC ISO-8601 records.
Connects to a local Ollama instance running Qwen3-Coder 30B. Employs prompt templates designed for log analysis, root-cause identification, and attack sequence mapping.
Interfaces with OpenCode to automate multi-agent task execution, enabling security tasks to run as background workers while preserving state and context across analysis sessions.
Executes on a dedicated Kali Linux environment, bridging local intelligence directly with native command-line forensic utilities and security inspection tools.
Data Isolation & Defensive Controls
Operational logs and system authentication details remain on localhost at all times; zero prompt data is transmitted to cloud endpoints.
Ingestion pipes operate with strictly read-only filesystem privileges, ensuring original system audit trails are never altered or damaged.
Analysis and triage tasks operate within authorized workspace directories, restricting background script execution to designated sandbox paths.
Local AI Model & Context Pipeline
CyberAI leverages Qwen3-Coder 30B served locally through Ollama. The model's large context window and strong code and structured syntax comprehension make it well-suited for security log interpretation:
Chunks continuous log streams into coherent temporal windows, allowing the model to detect coordinated activity distributed across multiple minutes or hours.
Synthesizes raw anomalies into qualitative severity flags (e.g. low-frequency reconnaissance vs. active credential brute-forcing) with transparent reasoning traces.
Testing & Telemetry Validation
The platform's log parsing and correlation modules are evaluated against synthetic and educational lab datasets:
Evaluated against simulated Linux authentication failure bursts, sudo privilege anomalies, and firewall connection drops to ensure accurate chronological reconstruction without dropped events.
Testing details, test event fixtures, and parser validation scripts are maintained in the project repository.
Active Development
Core log parsing, timeline ordering, and local Qwen3-Coder inference integrations are operational. Work is currently progressing on streaming socket ingestion and deeper OpenCode automation hooks.
Planned Improvements
- [Planned] Real-time streaming ingestion via systemd-journald socket listeners.
- [Planned] Automated Sigma rule matching integrated directly with local LLM threat correlation.
- [Planned] Interactive timeline filtering UI rendered within the local OpenCode environment.