by Aurakore

Sign in to the console

Use your Aurakore account. Every action you take here is recorded against your name.
The console reads the ledger and stages decisions for approval. Signing in identifies you on both.
No account? Excubitor accounts are made by an administrator of your workspace, or by us when a contract starts. Ask us for access or run the free reviewer on your own machine.
Overview
Sample data Chain POSTURE · READING

Welcome back.

Reading the ledger.

Deep trace This tenant
Ask Excubitor is not connected yet. Everything below reads the live ledger.
Needs attention Anything waiting on a person
Current state What the ledger says right now
Modules
Open a module to see what it found
Spaces: what you chose to keep
An answer worth returning to, kept where you can find it again. Nothing arrives here on its own: you keep an item, and keeping it is recorded in the ledger like any other action.

Settings

The applications reporting into this tenant, the people who can see them, and what your agreement covers. Issuing a credential and adding a person are administrator actions, and both are recorded in the ledger with your name on them.

Customers

Start an evaluation, set up a paying customer, change terms, resend an activation link or download a licence file. Evaluations start as soon as you confirm them. Anything a customer pays for waits for a second person to approve it. Everything here is recorded with your name.

Activity

Every change to this workspace and every decision taken in this console, with the person who made it. Administration comes from the workspace audit log; decisions come from the signed ledger and cannot be edited after the fact.

Decision Replay
Every box is one thing an AI did. Follow the arrows to see how a simple request became a $48,200 payment. Click any box to trace its story.
request tool call data AI output alert blocked poisoned
⚠
This $48,200 payment was poisoned 3 steps back. Hidden instructions in a document, not your request, created it. Excubitor traced it to the exact source and held it for your approval.
The chain, in order: out_pay48k
Contagion: how the problem spread
One poisoned document passed through four AI helpers. Each one, on its own, looked like it was doing its normal job, which is exactly why nothing else caught it.
4
AI helpers infected by one document
The hidden instruction rode along as each helper handed its work to the next. Blast radius grows with every hand-off.
CRITICALCross-agent contagionLLM01 → via LLM02ATLAS AML.T0051
A threat spread across 4 agents: mail-agent → parser-agent → invoice-copilot → payments-agent
A prompt-injection first seen in a document flowed through the system, and each hand-off passed data derived from the original threat. Each step looked fine on its own, so per-call guardrails let it through. Only a view of the whole ledger shows the payload crossing agent boundaries. The more helpers it touches, the wider the damage could be.
Next steps
Behavior: who acted out of character
Excubitor quietly learns what "normal" looks like for each AI helper. When one suddenly does something it has never done, that stands out, a strong sign it was tricked or hijacked.
Guard: every call, wrapped
Guard sits around each model and tool call: it checks the arguments, holds the rate limit, and records what happened. This is that record, gathered by tool.
Detect: what the detectors caught
Injection, PII and secret detectors run over the payloads passing through. Everything they raised is here, with what it maps to.
Gateway: in front of the tool servers
Every call an agent makes to another service goes through one chokepoint, so it is identified, rate-limited and recorded on its way out rather than noticed afterwards. This is what left the building.
Red Team: probes on a schedule
A standing set of adversarial probes runs against your agents and is scored into a report, so a defence that stopped working is noticed before an attacker finds it.
Assessment A scenario engagement, so it carries no chain attestation and cannot be mailed as a ledger report.
The full assessment, including the method notes and every scenario summarised here, comes with the report.
Remediation: contain, check, heal
What was done about a problem, and by whose authority. A reversible step runs on its own; anything destructive waits for a person, the same rule as a payment.
Discovery log
Every finding, from every agent, across every repository: one signed, append-only log rather than a conversation per pull request.
Loading
Excubitor by Aurakore · Every number on this page comes from your signed ledger.