Astrixion Docs

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:

  1. Inventory records what is known about a target.
  2. Acquisition and resolution bring in observations and associate them with the right scope.
  3. The distributed workflow engine turns a reusable scan definition into queued worker tasks and structured results.
  4. 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

Crawler / sync / operator


┌────────────────────┐       scope association       ┌──────────────────┐
│ Inventory          │◀──────────────────────────────│ AI resolution    │
│ programs · scopes  │                               └──────────────────┘
│ assets             │
└─────────┬──────────┘
          │ inputs and target bounds

┌──────────────────────────────┐
│ Distributed workflow engine  │
│ workflow → scan → tasks      │
└──────────┬───────────────────┘
           │ RabbitMQ

┌────────────────────┐       raw output       ┌──────────────────┐
│ Worker fleet       │───────────────────────▶│ MinIO            │
└─────────┬──────────┘                        └────────┬─────────┘
          │ result callback                            │
          └────────────────┬───────────────────────────┘

                  parse and upsert

                           └──────────────▶ Inventory

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

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.

On this page