Verifiable evidence
infrastructure for AWS
Evidence Verification

Verify a Yakuq EvidenceOps evidence package

Every evidence package produced by Yakuq EvidenceOps is cryptographically signed. Anyone can verify a package independently — no Yakuq account, no Yakuq software services, no network access required. Verification is performed by math, not by trust in a vendor. Including us.

01

The published signer fingerprint

Ed25519 · SHA-256

Compare this value against the fingerprint printed by the verification tool. They must match exactly.

PUBLISHED SIGNER FINGERPRINT

SHA-256
Yakuq EvidenceOps signing certificate
6b3869b9cd97e1f7d9526a2b42b1e0a27491cec07beb0c0b5439af8e8305f888

Paste the fingerprint your verification tool printed. It is checked against the published value above — any format works; colons, spaces, and letter case are ignored.

Nothing leaves your device — no network calls, no analytics, no storage. The comparison runs entirely in your browser.

02

Get the tool

Apache-2.0

Yakuq Verify is a single-file, open-source tool. Its only dependency is the cryptography library. Source: github.com/YakuqCloud/yakuq-evidence-verify

Install
$ pip install cryptography $ curl -LO https://raw.githubusercontent.com/YakuqCloud/yakuq-evidence-verify/main/yakuq_verify.py
03

Run the verification

Offline · no network
Verify a package
$ python yakuq_verify.py evidence-package.zip \ --expected-fingerprint 6b3869b9cd97e1f7d9526a2b42b1e0a27491cec07beb0c0b5439af8e8305f888
04

What the result means

Determination
Detection Limits

What the signature does not prove

That the collected data truthfully represents the AWS environment. That assurance comes from the collection design — read-only API access, per-call provenance recorded in the manifest, and every collector call visible in the customer’s own CloudTrail.