Daedalus¶
A hierarchical LLM agent orchestrator for autonomous security testing.
Daedalus runs a team of coordinating LLM agents — an executive that plans and delegates, and specialist workers (recon, web, pwn, rev, forensics) that do the work — against CTF and lab targets. Every action an agent takes runs inside an ephemeral, network-isolated sandbox. Agents can be driven by local models on your own GPU (via Ollama) or by a CLI-driven cloud model for the harder reasoning, with a hard per-team budget and three independent brakes so an autonomous run can never quietly overspend or escape its sandbox.
A mobile-first web console shows the board, live recon, findings, and activity.
Authorized use only
Daedalus automates offensive security tooling (scanners, brute-forcers, exploit frameworks). Use it exclusively against systems you own or are explicitly authorized to test — CTF platforms, your own lab, or engagements with written scope. You are responsible for what it does.
What it does¶
- Plans and delegates. An executive agent breaks an engagement into tasks and hands them to specialist workers, each scoped to a discipline.
- Acts in a sandbox. Every command an agent authors runs in a throwaway container on an isolated network — the blast radius of a rogue command is one disposable sandbox, never the control plane.
- Records findings. Hosts, services, vulnerabilities, and footholds are stored as structured data you can drill into, correlate by host, and export.
- Writes it up. A multi-pass report generator turns the recorded findings into a pentest report or a facilitator-ready tabletop exercise, grounded in a curated real-world reference library.
- Emulates an adversary at reach. Lightweight BAS agents dropped into other segments run ATT&CK techniques and measure what the defenders catch.
The name¶
Daedalus was the master craftsman of Greek myth — the architect who built the Labyrinth and forged self-moving automatons that acted on their own. The name fits a system whose job is to build and direct autonomous agents that navigate the maze of a target. It's also a caution worth keeping: Daedalus built the wings, but Icarus flew too close to the sun. The budget ceilings, the concurrency cap, and the sandbox isolation are the parts that keep this machine from doing that.
Where to go next¶
- Architecture — how the pieces fit and why the control plane never touches a target.
- Safety model — the three brakes and the sandbox network modes.
- RBAC & access — roles, features, and identity.
- Reports & tabletop — turning findings into a deliverable.
- Deploying agents — one-liners for Linux, macOS, and Windows.