Skip to content
quoxcli

See your security engagements

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-25.

See your security engagements

A security engagement is a scoped, risk-capped, witnessed piece of security work against your own estate. Ask Quox what is scoped, then list it, read the tools and verify the witness yourself.

What you get: a plain answer to “what security work is pointed at my estate”, backed by a list you can read yourself, the real catalogue of scan tools, and a witness on each engagement you can recompute. An engagement is not a free-for-all scanner: it is scoped to verified targets, capped by a risk ceiling, and does nothing until it is activated.

Ask Quox

Section titled “Ask Quox”

Ask in your own words what security work exists:

quox · talking to Quox

what engagements do I have

▤ AOCL │ L1 identity complete · allowed · 2ms

▤ AOCL │ L3 policy gate complete · proceed · 11ms

◐ SECURITY │ list engagements ✔ SECURITY │ list engagements │ 4 count, 4 engagements · 22.3s

⛓ AEE │ envelope opened · ops.tool · security_list_engagements ok

⛓ AEE │ envelope opened · stream_success

You have four security engagements. All are in draft, and all were created within the
last minute or so.

• Northwind Logistics discovery (dev tier, discovery ceiling), part of Internal review.
• Initech API review (dev tier, passive ceiling), part of Internal review.
• Globex staging audit (staging tier, safe_active ceiling), part of Customer pentests.
• Acme Retail external pentest (production tier, discovery ceiling), part of Customer
  pentests.

None are active yet. Acme Retail is the only one aimed at production, so I'd confirm its
scope and verification before it goes live. I can pull the details or findings for any
of them if you'd like.

42.8s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.1, 25 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 25 Oct 2026 · test report mvn6t9

Quox read the engagement store and did not just list rows: it noticed all four are still draft, so nothing has run, and flagged that the only production-tier one should have its scope confirmed before it goes live. It answers from the store, not a guess.

Do it yourself

Section titled “Do it yourself”

The chat answer came from the same place these commands read. Run them yourself.

1. List the engagements

Section titled “1. List the engagements”
every engagement, its environment and risk ceiling 
quox engagement listID                Name                            Status   Environment   Risk CeilingENG_01M5RCYD…     Acme Retail external pentest    draft    production    discoveryENG_01M5RCYG…     Globex staging audit            draft    staging       safe_activeENG_01M5RCYN…     Initech API review              draft    dev           passiveENG_01M5RCYP…     Northwind Logistics discovery   draft    dev           discovery
From the Quox Demo org. Trimmed, ids shortened.

The risk ceiling is the cap on what the engagement may ever do: a passive engagement can never run an active scan, whatever anyone asks. draft means it is set up but not activated, so nothing runs yet.

2. Read the scan tools

Section titled “2. Read the scan tools”
the real capability tools and their risk tier 
quox engagement toolsTool                 Risk          Binary      Descriptiondiscover_hosts       discovery     subfinder   Passive subdomain enumerationprobe_http           discovery     httpx       HTTP/HTTPS service probingresolve_dns          discovery     dig         DNS resolutioninspect_tls          discovery     openssl     TLS/certificate inspectionvuln_scan            safe_active   nuclei      Template-based vulnerability scanningport_scan            safe_active   nmap        Port/service version scanscan_secrets         discovery     gitleaks    Git repository secret scanningscan_image           discovery     trivy       Repository CVE scanning 12 items
From a real run on our own install. Trimmed.

Each tool carries a risk tier. A tool runs against a target only when the target is verified, in scope, and the tool’s tier is at or below the engagement’s ceiling. A tool above the ceiling is refused, not run.

Each engagement, and every finding under it, is witnessed on an append-only WARD chain, so the security record is tamper-evident: a silent edit after the fact breaks the chain. Check a receipt shows how to verify one witnessed record yourself.

What just happened

Section titled “What just happened”

You asked what security work is pointed at your estate and got an answer from the real engagement store, then read the same data yourself: the engagements with their risk ceilings and the catalogue of scan tools. No scan ran. Every command here only read, and the record behind it is witnessed rather than something you have to take on trust.

What this shows, and what it doesn’t

Section titled “What this shows, and what it doesn’t”
  • It shows what security work is scoped against your estate, the cap on each piece, the tools available, and that the record is witnessed and recomputable.
  • It does not run anything. Every engagement above is draft, and a scan only runs against a verified, in-scope target within the risk ceiling, as a separate step.
  • A verified witness proves integrity, not correctness. It proves the engagement and its findings were not altered after they were witnessed. It does not prove a finding is right, or that a scan found everything. Integrity after the fact, not correctness at capture time.

Check it yourself

Section titled “Check it yourself”

Each engagement’s witness is a position on a WARD chain, so any engagement can be checked against the record independently. Check a receipt shows the same idea for an approval. The witnessed evidence behind these pages is published and recomputable at quox.ai/evidence/explore.

Undo

Section titled “Undo”

Nothing to undo: every command here only reads and recomputes.

Next

Section titled “Next”