Sonar
Understand Sonar's Inventory, distributed workflow engine, interfaces, and operating model.
Sonar is Astrixion's private security-scan orchestration product. It maintains a shared inventory of programs, scopes, and discovered assets, and it runs reusable scan workflows across a fleet of disposable workers.
What Sonar does
Sonar separates four responsibilities that are easy to conflate:
- Inventory records what is known about a target.
- Acquisition and resolution bring in observations and associate them with the right scope.
- The distributed workflow engine turns a reusable scan definition into queued worker tasks and structured results.
- Interfaces and guides expose bounded capabilities to operators and agents without moving domain ownership out of the subsystems above.
In Sonar, a target is operator shorthand for a program, optionally narrowed to one scope. It is not a separate database entity.
How Sonar works
The result is a loop: current Inventory bounds the work; workflows collect new observations; the result pipeline writes those observations back into Inventory.
System map
Inventory
Programs, scopes, and discovered assets — plus acquisition, freshness, AI resolution, and verification. The canonical source of truth for what is known about a target.
Workflow engine
Workflows, scans, task execution, and the worker fleet — with command authoring and the consistency, recovery, and reliability qualities the runtime guarantees.
Sonar MCP
A bounded, profile-gated Model Context Protocol interface. It exposes Sonar capabilities to agents without owning the concepts it surfaces.
Guides
Goal-oriented operator and agent procedures — with prerequisites, verification, and troubleshooting — that link back to the canonical subsystems.
Public mechanisms, private credentials
The documentation and downloadable artifacts contain placeholders only. A bearer token, service identity, or worker bootstrap secret must come from the operator-controlled environment.