How usv240/argus-detection-evolution works
ARGUS is a live Splunk-backed adversarial detection-evolution product. A user launches an arena run; the backend repeatedly generates synthetic attack variants, evaluates the current detection against Splunk, and evolves the rule, then presents measured coverage and review artifacts. The graph preserves scenario definitions, provider integrations, scoring, export, and the human-approval path. Some subsystem details are documented in the README or source index rather than shown in excerpts, so those links cite that evidence and uncertain wiring is omitted.
Main entry points: arena_orchestrator.py Arena orchestrator · api.py HTTP API · red_synthesizer.py Red synthesizer · search.py Search provider selector
Components 21
User experience
- Application shell
frontend/src/App.tsx - Landing view
frontend/src/views/Landing.tsx - Arena view
frontend/src/views/Arena.tsx - Live event stream
frontend/src/api/stream.ts
Evolution engine
- HTTP API
backend/api.py - Arena orchestrator
backend/arena_orchestrator.py - Scenario definitions
backend/scenarios.py - Red synthesizer
backend/agents/red_synthesizer.py - Detection evaluator
backend/agents/evaluator.py - Blue evolver
backend/agents/blue_evolver.py - Reasoning model
backend/models/llm.py
Splunk integration
- Search provider selector
backend/splunk/search.py - MCP search client
backend/splunk/mcp_client.py - SDK search client
backend/splunk/sdk_client.py - Synthetic event writer
backend/splunk/hec.py
Results and review
- Anomaly scorer
backend/models/scorer.py - Splunk app export
backend/app_export.py - Saved-search approval
backend/splunk/sdk_client.py - Slack notifications
backend/slack_notifier.py
Other components
- Security analyst
- Splunk instance
Connections 26
- Security analyst → Application shell: opens
README.md - Application shell → Landing view: renders
frontend/src/App.tsx - Application shell → Arena view: renders
frontend/src/App.tsx - Arena view → Live event stream: receives updates
frontend/src/views/Arena.tsx - Arena view → HTTP API: requests runs
frontend/src/views/Arena.tsx - HTTP API → Arena orchestrator: starts runs
backend/api.py - Arena orchestrator → Scenario definitions: uses scenario
backend/arena_orchestrator.py - Arena orchestrator → Red synthesizer: requests variants
backend/arena_orchestrator.py - Arena orchestrator → Detection evaluator: scores detection
backend/arena_orchestrator.py - Arena orchestrator → Blue evolver: evolves rule
backend/arena_orchestrator.py - Red synthesizer → Reasoning model: proposes evasions
backend/agents/red_synthesizer.py - Blue evolver → Reasoning model: rewrites rule
backend/agents/blue_evolver.py - Red synthesizer → Scenario definitions: builds events
backend/agents/red_synthesizer.py - Red synthesizer → Synthetic event writer: writes variants
backend/agents/red_synthesizer.py - Detection evaluator → Search provider selector: runs SPL
backend/agents/evaluator.py - Scenario definitions → Search provider selector: queries distributions
backend/scenarios.py - Search provider selector → MCP search client: selects MCP
backend/splunk/search.py - Search provider selector → SDK search client: selects SDK
backend/splunk/search.py - MCP search client → Splunk instance: runs live searches
backend/splunk/mcp_client.py - SDK search client → Splunk instance: runs live searches
backend/splunk/sdk_client.py - Synthetic event writer → Splunk instance: ingests events
- Arena orchestrator → Anomaly scorer: scores variants
backend/arena_orchestrator.py - HTTP API → Splunk app export: exports app
backend/api.py - HTTP API → Saved-search approval: approves deployment
backend/api.py - Saved-search approval → Splunk instance: creates saved search
backend/splunk/sdk_client.py - HTTP API → Slack notifications: notifies
backend/api.py