Verification lab
Do not take our word for it. Run the tests.
Every substantive claim on this site is meant to be checkable in your own environment, with your own storage account, in an afternoon.
Tests
What to try.
- 01
Read your own bucket directly
Use the AWS console or the AWS CLI against the bucket you connected. Download an object RED wrote. It is ciphertext — there is no readable file, header or preview in your storage account.
- 02
Corrupt a chunk and try to open the file
Modify a single byte of a stored object, then open the document in RED. Authentication fails and the file refuses to open. It does not return partial or wrong plaintext.
- 03
Reorder or duplicate chunks
Swap two chunk objects in the bucket. Each chunk is bound to its position, so the read is rejected rather than silently reassembled in the wrong order.
- 04
Strip the manifest authentication fields
Remove the authentication fields from a document's manifest to try to force the older unauthenticated read path. The server-side authentication floor rejects the downgrade.
- 05
Revoke access and retry
Remove a member's authority, then have them attempt to open a previously accessible document. Authorization is short-lived and consumed atomically, so the retry is denied.
- 06
Test administrative separation
As an Owner or Admin, try to open a document that was never shared with you. Administration does not grant a wrapped key, so the open is denied.
- 07
Verify the cryptographic audit chain
Export the cryptographic event ledger and verify the hash chain. Each entry commits to the previous one, so any retroactive edit breaks verification.
What a failure would mean
The tests are designed to be able to fail.
A verification exercise that cannot produce a negative result is marketing. Each test above has a defined failure condition: if a tampered chunk opens successfully, if a reordered document reads correctly, if a revoked session keeps decrypting, the claim on this site is wrong and we want to know.
Want a guided verification session?
We will run these tests with your security team against an environment you control.