Information Security & Cryptography

Evidence You Can Inspect.

The public edition exposes verifiable publication evidence. Protected archives and security operations stay in the private local application.

Integrity

SHA-256

Aegis hashes content bytes using SHA-256. Public records include hashes of canonical UTF-8 metadata and analysis bytes. Every lineage step also hashes the previous chain value and its record.

Authenticity

Ed25519 Provenance

The existing ProvenanceService signs its canonical manifest body with Ed25519. Verification checks that signature, the complete lineage chain and every published content hash. This is Aegis provenance v1, not C2PA.

Confidentiality · Private Stack

AES-256-GCM

The local archive encryption implementation requires a 32-byte AES key and a 96-bit nonce. Authenticated data binds the algorithm, key ID, version and caller context. The persistent nonce allocator prevents reuse. No archive ciphertext, decryption keys or protected plaintext is included here.

Authorization · Private Stack

Access Control

The local API validates signed access tokens against configured issuer keys and checks scopes plus roles. Public browsing uses static files and has no token forms, administrator identity or write endpoint.

Accountability · Private Stack

Security Audit

Aegis records allowlisted actions and outcomes, hashes actor and subject identities, and discards non-allowlisted audit fields. Internal administrative audit records stay private. Public releases identify their source commit and export digest.

Verification

Tamper Detection

Changing metadata, analysis, lineage or signature bytes causes verification to fail. The private application retains the complete archive tampering and restoration demonstration. Public verification never writes or restores private data.

Verify A Published Record

Your browser uses Web Crypto to check SHA-256 and Ed25519 against the exact public bytes. Unsupported browsers report verification unavailable.

Ready To Verify In Your Browser.

Public Key Fingerprint · SHA-256

7b97868d73dda086e9fe52b9f27c5b965b2f0755496842c00113c67c59c48cd4

The verification key is pinned in the reviewed repository’s trust.json. A site-supplied key alone cannot establish publisher identity: compare this fingerprint with a separately trusted copy. The export key is dedicated to this showcase; this does not assert verification of private archive bytes.

A valid signature does not establish factual accuracy. It demonstrates consistency with the signer’s published bytes and key.