QSE Fleet — Command Center

connecting to control plane…

Live fleet roster from the orchestration control plane. Actions here are real: Register provisions a collector over SSH (per-device mTLS cert + deploy); Quarantine tells the control plane to stop merging a device's batches; Remove drops it from the roster (optionally uninstalling). Read-only quantum-risk analytics live in QPA's graph views — open them from 📊 Graph views (or the Graph deep-links in a device drawer); they read the same live Neo4j the sync daemon keeps in step with this control plane.

⇩ Export ▾
Portable analytics handoff
Interchange
CycloneDX CBOM (.cdx.json)
Configuration
🩺 Debug dump

Cloud Connectors

Read-only assume-role attachments. Each account below shows what was registered, every enabled service with its live scan state, and the ECS Fargate artifact jail status. Retry a failed service from its row. Use ☁ Connector Onboarding above to register another account.

Collector registry

No collector registry found

Device & type IP / host Cert CN Records Last seen Heartbeat Data Actions

Download

A qse-agent build, or the operator certificates as one folder.

Agents
Windows amd64 — qse-agent.exe Linux amd64 — qse-agent Linux arm64 — qse-agent
Certs
Download certificates

⌗ Deploy command spec (DSL)

Pushes a declarative collection profile to the control plane; collectors pull it on their next heartbeat. Applies fleet-wide (target shown for reference).

🩺 Pipeline health

every stage of the discover → normalize → analyze pipeline

loading…

↗ Full page

+ Register collector

Mints a per-device mTLS cert from the lab CA and provisions the target over SSH: Agent installs the resident Coordinator (Linux + a built qse-agent-ot + the Master key; else it falls back to the timer agent), Sniffer the passive sensor on a SPAN NIC, Agentless runs a one-shot remote scan.

☁ Connector Onboarding

Register a read-only assume-role so QSE can inventory cloud services. All collection is metadata-only — no private keys, secrets, or object contents.

This connector is granted read-only IAM actions only (List / Get / Describe). It cannot create, modify, or delete resources.

loading…
Select AWS to preview the template…

loading…

Scan settings

Defaults are filled in — change only what you need. 0 = unlimited. Settings are remembered per account for the next run.

Artifact scanning (Lambda & container images)

Uses the ECS jail saved on this account (ECS jail button on the card). Not set up yet? Choose Local only.

Logs & findings
Advanced caps

Per-collector caps (blank = collector default)

ECS Fargate artifact jail

Lambda zips and container images are unpacked and scanned inside your AWS account on ECS Fargate, so no artifact leaves it. Deploy the jail CloudFormation stack, enter its region and stack name, then Verify. The console reads the stack outputs in that region. Nothing below is a secret; the reader credentials and the encrypted scope are derived automatically at scan time.

Advanced — override stack outputs

⚠ AWS Preflight Warnings

The following potential issues were detected before the scan started. These warnings do not stop scanning — they are advisory only.