Excubitor platform · Agent Security

What an agent touched, and for whom.

A breach that spreads through one identity looks ordinary to every service it reaches. Excubitor keeps the footprint: who each record was for, every file an agent took in, every service an identity reached, every handoff from one agent to another, and every change an agent's tools made in other systems.

Request a walkthrough See editions

Ledger recordSample, illustrative values

{
  "type": "alert",
  "agent": "excubitor.enforce",
  "severity": "HIGH",
  "payload": {
    "phase": "identity",
    "decision": "flagged",
    "rule": "identity_fan_out",
    "subject": "person:3fa9c1d2",
    "service": "github",
    "new_in_window": 3,
    "credential": "cred_8e21…c4"
  },
  "evidence": {
    "chain": "sha256-chain/2",
    "prev": "02bb…9e"
  }
}

Hashes, not content. Chained to the record before it.

What it gives you

Follow one identity

Every record names the person or workload an agent acted for. A settled identity reaching a new service is flagged, and several within the hour is flagged high.

Know what came in

Every file that reaches an agent is recorded with what it said it was and what its bytes are. A file whose label lies is flagged, and can be refused before your parser opens it.

Know what changed

Every write an agent's tools sent to another system, whether it took, and the tool call behind it.

How it works

Agent Security, in four parts.

Credentials as fingerprints

An outbound request is tied to the credential it carried by a one-way value keyed with a secret you set. The credential itself is never written anywhere.

Files from every door

Images and documents in model requests, files a tool or server hands back, and your own parse step, with the parser and whether it raised.

Changes without content

The path keeps its words and loses its ids; a created id is hashed so it can be matched later without being stored.

Agent sandboxes

An agent sandbox's denials, findings and policy changes signed into the ledger, attributed to the agent; the sandbox stopped when the agent is contained.

Shipped

What is live, and since when.

Every item names the release that carries it. Releases are signed, and each lists the commands to check them before you install.

28 Sep 2026Excubitor 0.2.4
Agent sandbox decisions signed in; containment reaches the sandbox.
29 Sep 2026Excubitor 0.2.5
The identity trail, files taken in and changes made, each with its own report and console page.
29 Sep 2026Hosted
In the Aurakore ERP, every database row an agent's tool changes is a change record, linked to the call and the person.
30 Sep 2026Excubitor 0.2.6
Delegation records: every handoff from one agent to another, from which run, and for whom, with what was handed on kept as a hash.

What it does not do

The limits, said first.

A file's type is read from its first bytes; the whole file is not validated. Changes are seen for writes made through the two standard Python HTTP libraries while a tool runs.
A new service on its own is flagged, not stopped; an agent is contained when its identity is flagged three times in an hour. Identity history lives in each running process and can be rebuilt from the ledger.

See it run on your own agents.

Request a walkthrough Open the console

No standing vendor access, ever. Managed with evidence, never on faith.