Trail of Bits published on 11 Aug 2026 about signing Merkle tree heads for Signal's automatic key verification. Independent auditor. Open implementation. Clients can notice a split view if someone tries to hand out different keys to different people. That is the bar I want in the room when a vendor says "trust the app."
We are not Signal. Most of you are not Signal. The transferable part is smaller: someone outside the company has to be able to say the transparency log is a lie.
What we test when you store secrets
Can a user prove the key they see is the key the service published. Can we run a split-view. Is the "verified" badge backed by a log or by a CSS class. Penetration testing services for us include that class of check when you ship E2EE, device linking, or a "secure vault" feature. A login form fuzz is not the whole engagement.
Schneier, 18 Aug, pointed at research on LLMs and contextual integrity. Models leak stored context. Privacy prompts do not fix it. If your product keeps memory, the audit question is who can extract the memory, not whether the system card said "aligned."
Eight hours inside an EHR tenant is the ugly version of "nobody watched the log." That write-up is eight hours in someone else's EHR. Key transparency is the pretty version: you invited the outsider before the breach report.
We will try to break the story your badge tells. Request a quote if the last review never left the login form.
If your Merkle tree only has one signer, and that signer is you, you have a blog post, not a transparency system.
Sources
- How Trail of Bits helps verify the integrity of your Signal chats — Trail of Bits, 11 Aug 2026
- LLMs and Contextual Integrity — Schneier on Security, 18 Aug 2026