Verifying your evidence
An evidence export (Settings → Integrations → Evidence export, or arch-admin evidence export on a self-hosted
instance) is one ZIP file: your account’s audit log for a period, chained row by row, the evidence and approvals it
binds by digest, ArchBeagle’s signed checkpoints of the chain, the public keys that signed them, and the daily RFC 3161
timestamps from FreeTSA and Sectigo that prove when each checkpoint existed. You can check all of it yourself, offline,
without trusting ArchBeagle.
With ArchBeagle’s verifier
Download the verifier and check its SHA-256 against the one published beside it:
curl -O https://archbeagle.com/verify/archbeagle_verify.py
curl -O https://archbeagle.com/verify/archbeagle_verify.py.sha256
shasum -a 256 -c archbeagle_verify.py.sha256
It is one file, for Python 3.10 or later, using the standard library only. Run it isolated, so nothing on your machine or in the bundle runs with it:
python3 -I archbeagle_verify.py archbeagle-evidence-acme-2026-10-01-2026-11-01.zip
It checks, in order: every file against the manifest; every row’s hash; every link between rows, with no gap; every
checkpoint’s signature, its key, and the chain of checkpoints; every evidence record and approval against the digest
its row binds, and each sealed list; and every daily timestamp, with an inclusion proof up to the day’s root and the
authority’s token through openssl ts -verify when OpenSSL is present.
- Exit 0: everything it checked passed. Exit 1: something was changed: it names the file and line. Exit 2: nothing failed, but something couldn’t be checked (no timestamp yet, no OpenSSL, signatures sampled). Exit 3: the file isn’t a bundle.
--keys audit-keys.json: compare the bundle’s keys with the ones ArchBeagle publishes athttps://app.archbeagle.com/.well-known/argus/audit-keys.json. Fetch that yourself, at another time than the export.--ssh: also check each checkpoint’s SSHSIG.--all-signatures: without thecryptographypackage the verifier checks a sample of signatures (the first and last of each chain, every timestamped one and every key change); this checks them all, more slowly.--json: the report for machines.- The last rows: rows written after the newest checkpoint are chained but not yet signed; the report says how many. They are signed within the hour.
Run your own witness
A checkpoint you keep yourself means ArchBeagle can’t later show you a different history up to it. Add this workflow to a
repository of your own that ArchBeagle checks; daily, it asks ArchBeagle for your account’s newest signed checkpoint with GitHub’s
OIDC token (nothing to store) and keeps it as a workflow artifact, and, with commit-to-branch, as a commit to a branch
of that repository:
# .github/workflows/archbeagle-witness.yml
name: ArchBeagle witness
on:
schedule: [{ cron: "17 6 * * *" }]
workflow_dispatch: {}
permissions:
id-token: write
contents: write # read is enough without commit-to-branch
jobs:
witness:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4 # only for commit-to-branch
- uses: ArgusADR/argus/deploy/evidence/witness@main
with:
commit-to-branch: archbeagle-witness
Then check an export against what you kept:
git fetch origin archbeagle-witness && git worktree add witness origin/archbeagle-witness
python3 -I archbeagle_verify.py archbeagle-evidence-acme-2026-10-01-2026-11-01.zip --witness witness/archbeagle-witness
Each kept checkpoint inside the export’s period must be the same signed statement as the export’s, and its head the same row: anything else fails as “the history forks”. A kept checkpoint outside the period is noted, not checked.
With OpenSSL and ssh-keygen
Each checkpoint in checkpoints/<chain>/<seq>.* can be checked with standard tools. OpenSSL 3.0 or later (macOS’s
/usr/bin/openssl is LibreSSL and can’t: use Homebrew’s or a Linux one):
jq -r '.signatures[0].sig' checkpoints/account-42/1208.dsse.json | base64 -d > sig.bin
openssl pkeyutl -verify -pubin -inkey keys/<key_id>.pem -rawin \
-in checkpoints/account-42/1208.pae -sigfile sig.bin
# Signature Verified Successfully
OpenSSH 8.1 or later:
ssh-keygen -Y verify -f keys/allowed_signers -I archbeagle@app.archbeagle.com -n audit-checkpoint@argusadr.dev \
-s checkpoints/account-42/1208.pae.sig < checkpoints/account-42/1208.pae
# Good "audit-checkpoint@argusadr.dev" signature for archbeagle@app.archbeagle.com
And a day’s timestamp, against the root in anchors/<day>.json:
openssl ts -verify -digest <root> -in anchors/2026-11-09.freetsa.org.tsr -CAfile anchors/tsa/freetsa.org.pem
# Verification: OK
These check the signatures and timestamps only; the chain links, the record digests and the inclusion proofs need the verifier.