How adila-123-dev/cdaas works
This appears to be a deception-as-a-service system: honeypots produce interaction events, an agent forwards them, and a controller ingests them. The event contract explicitly describes MQTT transport and controller ingestion. Source excerpts for the runtime modules and README are empty, so internal call wiring and dashboard data flow cannot be confirmed; the graph omits those links.
Main entry points: agent/main.py Agent Runtime · event_schema.py Event Contract · forwarder.py Event Forwarder · app/main.py Controller Runtime
Components 11
Deception Nodes
- Honeypots
Node Agent
- Event Contract
shared/event_schema.py - Agent Runtime
agent/agent/main.py - Registration
agent/agent/registration.py - Config Applier
agent/agent/config_applier.py - Event Forwarder
agent/agent/forwarder.py - Heartbeat
agent/agent/heartbeat.py
Controller
- Controller Runtime
controller/app/main.py
Dashboard
- Dashboard
dashboard
Other components
- Attacker
- MQTT Broker
Connections 7
- Attacker → Honeypots: interacts with
- Honeypots → Agent Runtime: produces events for
- Event Contract → Agent Runtime: defines event format
- Agent Runtime → Event Forwarder: forwards events
- Event Forwarder → MQTT Broker: publishes events
- MQTT Broker → Controller Runtime: delivers events
- Event Contract → Controller Runtime: defines event format